| commit | ac9226cf8c496b15e369b2fcae95066f4a597a5b | |
| author | Jan Beulich <jbeulich@suse.com> | |
| Wed, 30 Nov 2022 08:06:33 +0000 (30 09:06 +0100) | ||
| committer | Jan Beulich <jbeulich@suse.com> | |
| Wed, 30 Nov 2022 08:06:33 +0000 (30 09:06 +0100) | ||
| tree | ee5644700ceb123597f406bfc9a09dbf29a7ca62 | treesnapshot (tar.gz zip) |
| parent | 3df781c5a459249fcb49e20ee36bdcd7bf111f0c | commitdiff |
x86: drop FloatR
There are just 4 templates using it, which can be easily identified by
other means, as D is set only on a very limited number of FPU templates.
Also move the respective conditional out of the code path taken by all
"reverse match" insns (it probably should have been this way already
before, to avoid the one conditional in the common case).
With this the templates which had FloatR dropped no longer differ from
their AT&T syntax + mnemonic counterparts - the only difference is now
which of the two would be recognized. For this, however, we don't need
two templates - we can simply arrange the condition for setting
Opcode_FloatR accordingly.
There are just 4 templates using it, which can be easily identified by
other means, as D is set only on a very limited number of FPU templates.
Also move the respective conditional out of the code path taken by all
"reverse match" insns (it probably should have been this way already
before, to avoid the one conditional in the common case).
With this the templates which had FloatR dropped no longer differ from
their AT&T syntax + mnemonic counterparts - the only difference is now
which of the two would be recognized. For this, however, we don't need
two templates - we can simply arrange the condition for setting
Opcode_FloatR accordingly.