This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1
- From: "rguenther at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 28 Apr 2016 13:48:26 +0000
- Subject: [Bug debug/68860] [6/7 regression] FAIL: gcc.dg/guality/pr36728-1.c -flto -O3 -g line 16/7 arg1 == 1
- Auto-submitted: auto-generated
- References: <bug-68860-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 28 Apr 2016, seurer at linux dot vnet.ibm.com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68860
>
> Bill Seurer <seurer at linux dot vnet.ibm.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |seurer at linux dot vnet.ibm.com
>
> --- Comment #9 from Bill Seurer <seurer at linux dot vnet.ibm.com> ---
> The pr36728 and pr68860 test cases that check the arguments (where the
> arguments are unused) all currently (and for a long time) fail on power. They
> show up as "optimized out" in gdb as in the initial report here.
>
> Is there some point to testing the value of the unused arguments in these test
> cases?
I think it is supposed to check the DW_TAG_GNU_call_site_parameter stuff.
You may want to double-check that is the case on x86_64 and debug why
the dwarf2out code doesn't work on ppc (it does some "interesting"
RTL deciphering which may not work on ppc for one or another reason)