public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: pinskia@gmail.com
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [rs6000] Fix compare debug failure on AIX
Date: Wed, 29 Apr 2015 10:37:00 -0000	[thread overview]
Message-ID: <EC523869-02C0-48DA-98B2-DFB5AE96D290@gmail.com> (raw)
In-Reply-To: <1633828.L6eKc0dpVU@polaris>





> On Apr 29, 2015, at 3:22 AM, Eric Botcazou <ebotcazou@adacore.com> wrote:
> 
> You can easily get -fcompare-debug failures on AIX with small functions, in 
> fact you get the failure for the empty function:
> 
> void foo (void) {}
> 
> eric@polaris:~/build/gcc/powerpc-ibm-aix7.1> gcc/xgcc -Bgcc -S t.c -O -
> fcompare-debug
> xgcc: error: t.c: -fcompare-debug failure (length)
> 
> Fixed thusly, tested on powerpc-ibm-aix7.1, OK for the mainline?
> 
> 
> 2015-04-29  Eric Botcazou  <ebotcazou@adacore.com>
> 
>    * config/rs6000/rs6000.c (rs6000_stack_info): For XCOFF, replace test
>    on debug info with test on optimization to decide stack pushing.

We might want to check if doing -Og and not just -O0. 

Thanks,
Andrew

> 
> 
> 2015-04-29  Eric Botcazou  <ebotcazou@adacore.com>
> 
>    * gcc.dg/empty3.c: New test.
> 
> 
> -- 
> Eric Botcazou
> <p.diff>
> <empty3.c>

  reply	other threads:[~2015-04-29 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 10:31 Eric Botcazou
2015-04-29 10:37 ` pinskia [this message]
2015-04-30 11:35   ` Eric Botcazou
2015-05-01 13:48     ` David Edelsohn
2015-05-02  4:24       ` Alan Modra
2015-05-02 10:05       ` Eric Botcazou
2015-05-04  0:32         ` David Edelsohn
2015-05-04  8:33           ` Richard Biener
2015-05-04 13:26           ` Tristan Gingold
2015-05-11  8:25           ` Eric Botcazou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=EC523869-02C0-48DA-98B2-DFB5AE96D290@gmail.com \
    --to=pinskia@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=ebotcazou@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).