public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/47785] GCC with -flto does not pass options to the assembler
Date: Fri, 18 Feb 2011 12:27:00 -0000	[thread overview]
Message-ID: <bug-47785-4-Wc4WXkPUnc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47785-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47785

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011.02.18 12:00:41
     Ever Confirmed|0                           |1

--- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-02-18 12:00:41 UTC ---
Confirmed.


  reply	other threads:[~2011-02-18 12:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 16:56 [Bug driver/47785] New: " d.g.gorbachev at gmail dot com
2011-02-18 12:27 ` rguenth at gcc dot gnu.org [this message]
2011-11-02 15:01 ` [Bug driver/47785] " rguenth at gcc dot gnu.org
2014-06-12 18:01 ` m8r-540gv7 at mailinator dot com
2014-06-12 18:18 ` dominiq at lps dot ens.fr
2014-06-12 18:20 ` dominiq at lps dot ens.fr
2015-07-17 14:01 ` ray.kinsella at intel dot com
2015-09-23 12:11 ` dominiq at lps dot ens.fr
2020-07-16 22:19 ` [Bug driver/47785] GCC with -flto does not pass -Wa/-Xassembler " mark at gcc dot gnu.org
2021-04-09 16:56 ` hjl.tools at gmail dot com
2021-04-12 12:29 ` cvs-commit at gcc dot gnu.org
2021-06-19  7:46 ` gcc@t-8ch.de
2021-07-15 17:48 ` hjl.tools at gmail dot com

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=bug-47785-4-Wc4WXkPUnc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).