public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark 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 -Wa/-Xassembler options to the assembler
Date: Thu, 16 Jul 2020 22:19:20 +0000	[thread overview]
Message-ID: <bug-47785-4-Vrx940X8Bg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47785-4@http.gcc.gnu.org/bugzilla/>

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

Mark Wielaard <mark at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at gcc dot gnu.org

--- Comment #18 from Mark Wielaard <mark at gcc dot gnu.org> ---
Since this patch has been included in gcc10 (I verified it works now, but fails
with gcc9) can this issue be closed? Or does it need backporting to earlier
versions?

  parent reply	other threads:[~2020-07-16 22:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 16:56 [Bug driver/47785] New: GCC with -flto does not pass " d.g.gorbachev at gmail dot com
2011-02-18 12:27 ` [Bug driver/47785] " rguenth at gcc dot gnu.org
2011-11-02 15:01 ` 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 ` mark at gcc dot gnu.org [this message]
2021-04-09 16:56 ` [Bug driver/47785] GCC with -flto does not pass -Wa/-Xassembler " 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-Vrx940X8Bg@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).