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] New: [12 Regression] Assembler error building glibc for ColdFire soft-float
Date: Mon, 22 Nov 2021 23:36:07 +0000	[thread overview]
Message-ID: <bug-103370-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103370
           Summary: [12 Regression] Assembler error building glibc for
                    ColdFire soft-float
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: assemble-failure
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jsm28 at gcc dot gnu.org
                CC: rguenth at gcc dot gnu.org
  Target Milestone: ---
            Target: m68k*-*-*

Created attachment 51849
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51849&action=edit
preprocessed source

Compile and assemble the attached preprocessed source (from glibc) with -O2
-fPIC -c, using a compiler configured for m68k-linux-gnu --with-arch=cf
--with-cpu=54455 --disable-multilib (this is m68k-linux-gnu-coldfire-soft in
build-many-glibcs.py).  This produces an assembler error:

/tmp/cctaeK7A.s: Assembler messages:
/tmp/cctaeK7A.s: Fatal error: Tried to convert PC relative branch to absolute
jump

This appeared with

commit 045206450386bcd774db3bde0c696828402361c6
Author: Richard Biener <rguenther@suse.de>
Date:   Fri Nov 12 10:21:22 2021 +0100

    tree-optimization/102880 - improve CD-DCE

though I'm guessing it was most likely to have been latent before then.

             reply	other threads:[~2021-11-22 23:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 23:36 jsm28 at gcc dot gnu.org [this message]
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
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@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).