public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: ramrad01@arm.com
Cc: "gcc-patches@gcc.gnu.org ," <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC] Fix for PR driver/47785
Date: Wed, 23 Jan 2013 15:36:00 -0000	[thread overview]
Message-ID: <CAFiYyc0TKe+PAAHfgLvNbujkJi9R4Tri6sjxrLGYkqfCTraJQA@mail.gmail.com> (raw)
In-Reply-To: <50FEB78A.6050709@arm.com>

On Tue, Jan 22, 2013 at 5:00 PM, Ramana Radhakrishnan <ramrad01@arm.com> wrote:
> Hi,
>
> I ran into PR driver/47785 when doing some testing with an option passed to
> the testsuite and I chose to fix this by putting out COLLECT_AS_OPTIONS as
> though these are options for the driver by prepending them with a "'-Wa",
> and suffixing them with a "'" character and additionally providing spaces as
> duly required. I've chosen a simple implementation.
>
> Tested in the past with x86_64-linux-gnu and arm-none-eabi cross tests (with
> an additional -Wa option passed to the default flags in a site.exp)
>
> Thoughts ?
>
> Ok for trunk now or should I stage this for 4.9 ?

I don't think this fix will work reliably - it's probably desirable
anyway for other uses
of -Wa,... but providing a symbol definition is something that needs
to be understood
by LTO at WPA time, otherwise we will get confusing / wrong symbol
resolutions and
eventually wrong code generated in the end.  Thus with the patch you get some
false sense of security I think (consider -fno-fat-lto-objects, you'd
get x UNDEFed,
and with -ffat-lto-objects you'd get a prevailing IRONLY def but the
symbol wasn't
in the LTO symbol table and we don't find a prevailing definition at
WPA time ...)

Thus, I think it at least has to wait ;)

Richard.

> regards,
> Ramana
>
>
> gcc/
>
> <DATE>  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>
>
>     PR driver/47785
>         * gcc.c (set_collect_as_options): New.
>          (main): Call this.
>         * lto-wrapper.c (run_gcc): Handle COLLECT_AS_OPTIONS.
>
>
> testsuite/
>
> <DATE>  Ramana Radhakrishnan  <ramana.radhakrishnan@arm.com>
>
>         PR driver/47785
>         * gcc.dg/pr47785.c: New test.
>
>
>

  reply	other threads:[~2013-01-23 15:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50C9F154.6090007@arm.com>
2013-01-22 16:00 ` Ramana Radhakrishnan
2013-01-23 15:36   ` Richard Biener [this message]
2013-01-23 15:50     ` Ramana Radhakrishnan
2013-01-23 15:53       ` Richard Biener
2013-01-23 15:53         ` Ramana Radhakrishnan

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=CAFiYyc0TKe+PAAHfgLvNbujkJi9R4Tri6sjxrLGYkqfCTraJQA@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ramrad01@arm.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).