From: Alexandre Oliva <aoliva@redhat.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: PATCH to run autoconf tests with C++ compiler
Date: Mon, 25 May 2015 21:05:00 -0000 [thread overview]
Message-ID: <orsiak8kpg.fsf@livre.home> (raw)
In-Reply-To: <555EA4B1.8090706@redhat.com> (Jason Merrill's message of "Thu, 21 May 2015 23:38:25 -0400")
On May 22, 2015, Jason Merrill <jason@redhat.com> wrote:
> * configure.ac: Use C++ for all tests. Use AC_CHECK_DECLS for
> strstr and basename.
> * configure: Regenerate.
This is ok, thanks.
I have one concern about scenarios in which config.cache is shared by
all builds for the host, but in which stage1 and stage2 compilers might
(and arguably should) get different results because of stage1's
-std=c++98, but with a shared config.cache, they won't. config.cache is
disabled by default, but I have it enabled and shared, so I might catch
any fallout from this change, so I'll keep my eyes open. It's not like
we couldn't have run into this before, due to differences between the
system C compiler and stage1, so... /me crosses fingers ;-)
--
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 Brasil GNU Toolchain Engineer
next prev parent reply other threads:[~2015-05-25 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 7:45 Jason Merrill
2015-05-25 21:05 ` Alexandre Oliva [this message]
2015-05-26 7:07 ` Alexandre Oliva
2015-05-27 10:02 ` Andreas Schwab
2015-05-27 13:32 ` Richard Biener
2015-05-27 16:20 ` Jason Merrill
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=orsiak8kpg.fsf@livre.home \
--to=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.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).