From: Sandra Loosemore <sandra@codesourcery.com>
To: Jeff Law <law@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, <chertykov@gmail.com>,
<rsonar.jayant@gmail.com>, Jeff Prothero <jprother@altera.com>
Subject: Re: [rfc, stage 1] default to -fno-delete-null-pointer-checks on nios2-elf
Date: Fri, 01 May 2015 20:34:00 -0000 [thread overview]
Message-ID: <5543E328.80205@codesourcery.com> (raw)
In-Reply-To: <552F3DA7.5090305@redhat.com>
Re https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01510.html :
On 04/15/2015 10:42 PM, Jeff Law wrote:
> It looks very sane to me. This is probably how the AVR and CR16 should
> have been handled to begin with IMHO.
>
> FWIW, I generally discourage ports overriding default options, but this
> is a case where I believe it makes some sense.
>
> Please move forward with an official submission.
I've now bootstrapped and regression-tested the previously posted patch
on x86_64-linux-gnu, as well as retesting it on nios2-elf after updating
my source tree to current mainline head.
Are the target-independent parts OK to commit?
-Sandra
next prev parent reply other threads:[~2015-05-01 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-29 19:31 Sandra Loosemore
2015-04-08 1:36 ` Sandra Loosemore
2015-04-16 4:42 ` Jeff Law
2015-05-01 20:34 ` Sandra Loosemore [this message]
2015-05-04 17:24 ` Jeff Law
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=5543E328.80205@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jprother@altera.com \
--cc=law@redhat.com \
--cc=rsonar.jayant@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).