From: Mike Stump <mikestump@comcast.net>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix up compat.exp C testing
Date: Wed, 02 Jan 2013 18:31:00 -0000 [thread overview]
Message-ID: <703419C2-4DD6-409F-9B33-DA076273039B@comcast.net> (raw)
In-Reply-To: <20130102125818.GQ2315@tucnak.redhat.com>
On Jan 2, 2013, at 4:58 AM, Jakub Jelinek <jakub@redhat.com> wrote:
> Anyway, this fixes the most urgent issue. Ok for trunk?
Ok. If you find any breakage in the patch and need to fix it, ok for that as well. :-o
For a fun time, compat testing clang and gcc would be a curious test.
> 2013-01-02 Jakub Jelinek <jakub@redhat.com>
>
> * lib/c-compat.exp (compat-use-alt-compiler): Remove
> -fno-diagnostics-show-caret from TEST_ALWAYS_FLAGS if needed.
> (compat-use-tst-compiler): Restore TEST_ALWAYS_FLAGS.
> (compat_setup_dfp): Initialize compat_alt_caret and
> compat_save_TEST_ALWAYS_FLAGS.
prev parent reply other threads:[~2013-01-02 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 12:58 Jakub Jelinek
2013-01-02 18:31 ` Mike Stump [this message]
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=703419C2-4DD6-409F-9B33-DA076273039B@comcast.net \
--to=mikestump@comcast.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).