public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100181] hot-cold partitioned code doesn't assemble
Date: Wed, 21 Apr 2021 12:52:06 +0000	[thread overview]
Message-ID: <bug-100181-4-fMRqoaKGmB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100181-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #7)
> (I could not reproduce the LLVM 9 issue in PR94278 back then.)

Hmm, but didn't you say in the LLVM issue
<https://bugs.llvm.org/show_bug.cgi?id=45887> (liked to in _See Also_ in
PR94278) that you _did_ reproduce this back then?  (Just making sure that it's
not actually a different issue that we're discussing now?)

  parent reply	other threads:[~2021-04-21 12:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 12:19 [Bug target/100181] New: " rguenth at gcc dot gnu.org
2021-04-21 12:22 ` [Bug target/100181] " rguenth at gcc dot gnu.org
2021-04-21 12:23 ` rguenth at gcc dot gnu.org
2021-04-21 12:25 ` rguenth at gcc dot gnu.org
2021-04-21 12:26 ` rguenth at gcc dot gnu.org
2021-04-21 12:27 ` tschwinge at gcc dot gnu.org
2021-04-21 12:32 ` rguenth at gcc dot gnu.org
2021-04-21 12:43 ` burnus at gcc dot gnu.org
2021-04-21 12:52 ` tschwinge at gcc dot gnu.org [this message]
2021-04-21 14:42 ` burnus at gcc dot gnu.org
2021-07-19 15:59 ` burnus at gcc dot gnu.org
2021-07-19 16:00 ` burnus at gcc dot gnu.org
2022-02-11 14:08 ` burnus at gcc dot gnu.org
2022-02-11 14:27 ` ams at gcc dot gnu.org
2022-05-27 19:44 ` tschwinge at gcc dot gnu.org

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-100181-4-fMRqoaKGmB@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).