public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88917] [9/10/11/12 Regression] Error: can't resolve `.text' {.text section} - `.LCFI2' {.text.unlikely section} with -fno-dwarf2-cfi-asm -mindirect-branch=thunk-inline
Date: Wed, 29 Dec 2021 01:43:00 +0000	[thread overview]
Message-ID: <bug-88917-4-CZHhXXLQYy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88917-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2019-01-18 00:00:00         |2021-12-28
      Known to fail|                            |12.0

--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The original testcase does not fail on the trunk any more due to VRP/jump
threading stuff but here is one which will fail:
int a, x;
unsigned short b, c;

void
foo(void (*bar)(void))
{
  bar();
  c *= a < x;
  if (c == 0) __builtin_trap();
  b /= c;
}

  parent reply	other threads:[~2021-12-29  1:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-88917-4@http.gcc.gnu.org/bugzilla/>
2021-05-14  9:51 ` jakub at gcc dot gnu.org
2021-06-01  8:12 ` rguenth at gcc dot gnu.org
2021-12-29  1:43 ` pinskia at gcc dot gnu.org [this message]
2022-05-27  9:40 ` [Bug target/88917] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:36 ` jakub at gcc dot gnu.org
2023-07-07 10:34 ` [Bug target/88917] [11/12/13/14 " rguenth 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-88917-4-CZHhXXLQYy@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).