public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/108250] [12/13 regression] llvm-tblgen miscompiled on powerpc-unknown-linux-gnu since r12-5383-g22c242342e38eb
Date: Thu, 29 Dec 2022 00:06:38 +0000	[thread overview]
Message-ID: <bug-108250-4-gz7RZWmTHh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108250-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Sam James <sam at gentoo dot org> ---
Flags used to build LLVM:
export FFLAGS='-O2 -mcpu=powerpc -mtune=powerpc -pipe'
export CXXFLAGS='-O2 -mcpu=powerpc -mtune=powerpc -pipe -ggdb
-D_GLIBCXX_ASSERTIONS=1'
export LDFLAGS='-Wl,-O1 -Wl,--as-needed'
export FCFLAGS='-O2 -mcpu=powerpc -mtune=powerpc -pipe'
export CFLAGS='-O2 -mcpu=powerpc -mtune=powerpc -pipe -ggdb'

LLVM was built at llvm-project.git commit
a4e3457fb752d675c58fb14a3d8ed03fe218b6b0
for the bisect.

_GLIBCXX_ASSERTIONS seemed to make the miscompilation more likely, anecdotally,
but
the original bug reported in Gentoo didn't have this set, and I reproduced the
hang
without it. But it seems more likely to happen when it's set.

  parent reply	other threads:[~2022-12-29  0:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-28 23:35 [Bug c/108250] New: " sam at gentoo dot org
2022-12-28 23:55 ` [Bug c/108250] " sam at gentoo dot org
2022-12-29  0:04 ` sam at gentoo dot org
2022-12-29  0:06 ` sam at gentoo dot org [this message]
2022-12-29  2:13 ` [Bug ipa/108250] " pinskia at gcc dot gnu.org
2022-12-29  2:48 ` sam at gentoo dot org
2022-12-29  3:14 ` sam at gentoo dot org
2022-12-29 16:54 ` arsen at aarsen dot me
2022-12-29 17:22 ` arsen at aarsen dot me
2023-01-02  3:44 ` pinskia at gcc dot gnu.org
2023-01-02  3:46 ` pinskia at gcc dot gnu.org
2023-01-03  1:18 ` sam at gentoo dot org
2023-01-09 14:09 ` rguenth at gcc dot gnu.org
2023-01-13 16:59 ` segher at gcc dot gnu.org
2023-03-27 12:27 ` rguenth at gcc dot gnu.org
2023-05-08 12:26 ` [Bug ipa/108250] [12/13/14 " rguenth at gcc dot gnu.org
2023-05-14 12:06 ` arsen at gcc dot gnu.org
2024-03-28  3:27 ` [Bug ipa/108250] [12/13 " sjames at gcc dot gnu.org
2024-03-28  3:31 ` sjames at gcc dot gnu.org
2024-06-20  9:11 ` rguenth at gcc dot gnu.org
2024-10-14 21:30 ` sjames at gcc dot gnu.org
2024-10-16  3:12 ` sjames 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-108250-4-gz7RZWmTHh@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).