[Bug gas/30317] .insn directive did not swap sources

[jbeulich at suse dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=30317

Jan Beulich  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Jan Beulich  ---
(In reply to Haochen Jiang from comment #0)
> For the current AMX and AMX-FP16 bad testcases, we got testcases like this:
> 
> #tdpfp16ps %tmm5,%tmm4,%tmm3 set VEX.W = 1 (illegal value).
> .insn VEX.128.F2.0F38.W1 0x5c, %tmm4, %tmm5, %tmm3
> .fill 0x05, 0x01, 0x90
> 
> #tdpfp16ps %tmm5,%tmm4,%tmm3 set VEX.L = 1 (illegal value).
> .insn VEX.256.F2.0F38.W0 0x5c, %tmm4, %tmm5, %tmm3
> .fill 0x05, 0x01, 0x90
> 
> The operand order is reversed for operand 2 and 3.

And intentionally so.

> I did not fully root cause the reason but I guess the highest possibility is
> the AMX instructions are using SwapSources which swaps operand 2 and 3.

SwapSources can only sensibly be present / in use for real insn templates.
.insn has to assume some specified ordering of operands, no matter what order
they ought to be in for the real (properly mnemonic-ized) insn. Please read the
documentation, which specifically states this aspect.

Of course syntax of .insn could be extended to allow specifying such, but I'm
afraid that would become unwieldy, because _all_ possible permutations would
then need to be expressable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Issue 57742 in oss-fuzz: binutils:fuzz_objcopy: Direct-leak in xrealloc

[sheriffbot via monorail]

Updates:
Labels: -restrict-view-commit

Comment #2 on issue 57742 by sheriffbot: binutils:fuzz_objcopy: Direct-leak in 
xrealloc
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57742#c2

This bug has been fixed. It has been opened to the public.

- Your friendly Sheriffbot

-- 
You received this message because:
  1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.

[Bug gas/30317] .insn directive did not swap sources

[haochen.jiang at intel dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=30317

--- Comment #3 from Haochen Jiang  ---
(In reply to Jan Beulich from comment #2)
> SwapSources can only sensibly be present / in use for real insn templates.

Yes since when we are in s_insn(), we actually did not know whether it is swap
source.

> 
> Of course syntax of .insn could be extended to allow specifying such, but
> I'm afraid that would become unwieldy, because _all_ possible permutations
> would then need to be expressable.

I get your point here. I suppose adding those might be overloaded for .insn.
Thx!

-- 
You are receiving this mail because:
You are on the CC list for the bug.

ORIGIN Grammar Typo in Some Documentation

[segaloco]

Hello, just reporting that lines 492-494 of ld/ld.texi contain examples of 
MEMORY ORIGIN of the form:

ORIGIN : offset

Where the grammar is:

origin_spec:
ORIGIN '=' mustbe_exp
{
  region->origin_exp = $3; 
}
;

Seems like hoops to raise a pull request, someone else can take the glory.

- Matt G.