From: Alexandre Oliva <aoliva@redhat.com>
To: Eric Botcazou <ebotcazou@adacore.com>
Cc: Richard Guenther <richard.guenther@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: fix -fcompare-debug regression in free_lang_data
Date: Mon, 16 Nov 2009 23:32:00 -0000 [thread overview]
Message-ID: <ord43ivyvu.fsf@livre.localdomain> (raw)
In-Reply-To: <200911081057.30326.ebotcazou@adacore.com> (Eric Botcazou's message of "Sun, 8 Nov 2009 10:57:29 +0100")
On Nov 8, 2009, Eric Botcazou <ebotcazou@adacore.com> wrote:
>> A patch to remove it is pre-approved (if that passes bootstrap &
>> regtest of course).
> If you remove the flag_gtoggle test, you will end up generating
> different code with -gtoggle -g0 and -gtoggle -g for the languages
> whose boolean_type_node is changed, thus breaking bootstrap
> comparison.
Yep. I can get bootstrap compare to pass using a non-default
BUILD_CONFIG, but with bootstrap-debug it fails as expected. Should I
check it in and expose the existing breakage, or leave it papered over?
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Compiler Engineer
next prev parent reply other threads:[~2009-11-16 23:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 7:46 Alexandre Oliva
2009-10-16 9:56 ` Richard Guenther
2009-10-17 7:17 ` Alexandre Oliva
2009-10-17 11:24 ` Richard Guenther
2009-11-08 7:27 ` Alexandre Oliva
2009-11-08 9:56 ` Richard Guenther
2009-11-08 10:02 ` Eric Botcazou
2009-11-08 10:17 ` Richard Guenther
2009-11-08 11:20 ` Eric Botcazou
2009-11-16 23:32 ` Alexandre Oliva [this message]
2009-11-17 8:17 ` Eric Botcazou
2009-11-17 15:54 ` Richard Guenther
2009-11-18 8:32 ` Alexandre Oliva
2009-11-09 0:51 ` Alexandre Oliva
2009-11-09 10:17 ` Richard Guenther
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=ord43ivyvu.fsf@livre.localdomain \
--to=aoliva@redhat.com \
--cc=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).