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/103370] [12/13 Regression] Assembler error building glibc for ColdFire soft-float
Date: Thu, 16 Feb 2023 18:14:04 +0000	[thread overview]
Message-ID: <bug-103370-4-an3x7crhJN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103370-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
The glibc build failure has done away and come back at least once since my
previous comment. It came back (I think the most recent time) with

commit 4fa25a7eb322f0a003c1eb15680c71ece345e01e
Author:     Martin Liska <mliska@suse.cz>
AuthorDate: Mon Jan 24 15:45:38 2022 +0100
Commit:     Martin Liska <mliska@suse.cz>
CommitDate: Wed Nov 30 14:03:43 2022 +0100

    Improve profile handling in switch lowering.

            PR tree-optimization/101301
            PR tree-optimization/103680

though that's almost surely just exposing a back-end bug. However, the reduced
test here gave a different assembler error

/tmp/cc40cNSh.s: Assembler messages:
/tmp/cc40cNSh.s:320: Error: syntax error -- statement `lea
(.LC0@GOT+3,%a5),%a0' ignored
/tmp/cc40cNSh.s:328: Error: syntax error -- statement `lea
(.LC1@GOT+3,%a5),%a2' ignored

both before and after that commit (different register numbers and .s line
numbers before versus after). Despite the different error messages from the
reduced test and building glibc, they are still likely to be the same bug in
the m68k back end.

  parent reply	other threads:[~2023-02-16 18:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 23:36 [Bug target/103370] New: [12 " jsm28 at gcc dot gnu.org
2021-11-22 23:43 ` [Bug target/103370] " pinskia at gcc dot gnu.org
2021-11-22 23:49 ` pinskia at gcc dot gnu.org
2021-11-23  7:37 ` rguenth at gcc dot gnu.org
2021-11-23  9:38 ` marxin at gcc dot gnu.org
2021-12-07 21:19 ` jsm28 at gcc dot gnu.org
2022-01-03  7:51 ` rguenth at gcc dot gnu.org
2022-05-06  8:31 ` [Bug target/103370] [12/13 " jakub at gcc dot gnu.org
2023-02-16 18:14 ` jsm28 at gcc dot gnu.org [this message]
2023-05-08 12:23 ` [Bug target/103370] [12/13/14 " rguenth at gcc dot gnu.org
2024-01-02 14:11 ` fw 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-103370-4-an3x7crhJN@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).