public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/106282] [10/11/12/13 Regression] m68k: Problem with thread-local storage and -mcpu=5206 since r9-2326-gede9446c26a929 Date: Thu, 16 Feb 2023 18:29:59 +0000 [thread overview] Message-ID: <bug-106282-4-mnQaiuCPlM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106282-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106282 Joseph S. Myers <jsm28 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |10.5 Summary|m68k: Problem with |[10/11/12/13 Regression] |thread-local storage and |m68k: Problem with |-mcpu=5206 since |thread-local storage and |r9-2326-gede9446c26a929 |-mcpu=5206 since | |r9-2326-gede9446c26a929 CC| |jsm28 at gcc dot gnu.org --- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> --- My glibc bot has been failing for ColdFire since some time between commits 79d38dd46e6b07e5a90ab25df1438eb0918eb475 and f56d48b2471c388401174029324e1f4c4b84fcdb, with an assembler error building libgomp (affinity-fmt.c) that looks just like the one in this bug. affinity-fmt.s: Assembler messages: affinity-fmt.s:4062: Error: syntax error -- statement `lea (gomp_tls_data@TLSLE+8,%a0),%a0' ignored https://sourceware.org/pipermail/libc-testresults/2022q4/010394.html Although that's from October 2022, I expect it's the same underlying issue, and just was latent building libgomp until some other change exposed it there. Note: soft-float ColdFire now fails earlier in my bot, failing to build glibc with bug 103370 (also an assembler error, also probably latent for some time before being exposed by an unrelated change).
next prev parent reply other threads:[~2023-02-16 18:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-13 13:30 [Bug target/106282] New: m68k: Problem with thread-local storage and -mcpu=5206 sebastian.huber@embedded-brains.de 2022-07-14 8:25 ` [Bug target/106282] m68k: Problem with thread-local storage and -mcpu=5206 since r9-2326-gede9446c26a929 marxin at gcc dot gnu.org 2023-02-16 18:29 ` jsm28 at gcc dot gnu.org [this message] 2023-02-21 14:07 ` [Bug target/106282] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org 2023-03-26 20:36 ` cvs-commit at gcc dot gnu.org 2023-03-27 20:06 ` schwab@linux-m68k.org 2023-07-07 10:43 ` [Bug target/106282] [11/12 " 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-106282-4-mnQaiuCPlM@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: linkBe 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).