On Mon, Sep 11, 2023 at 07:27:57PM +0200, Benjamin Priour via Gcc-patches wrote:
> Thanks for the report,
>
> After investigation it seems the location of the new dejagnu directive for
> C++ differs depending on the configuration.
> The expected warning is still emitted, but its location differ slightly.
> I expect it to be not an issue per se of the analyzer, but a divergence in
> the FE between the two configurations.
I think the divergence is whether called_by_test_5b returns the struct
in registers or in memory. If in memory (like in the x86_64 -m32 case), we have
[compound-assignment-1.c:71:21] D.3191 = called_by_test_5b (); [return slot
optimization]
[compound-assignment-1.c:71:21 discrim 1] D.3191 ={v} {CLOBBER(eol)};
[compound-assignment-1.c:72:1] return;
in the IL, while if in registers (like x86_64 -m64 case), just
[compound-assignment-1.c:71:21] D.3591 = called_by_test_5b ();
[compound-assignment-1.c:72:1] return;
If you just want to avoid the differences, putting } on the same line as the
call might be a usable workaround for that.
Jakub
