public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104208] New: -mlong-double-64 should override a previous -mabi=ibmlongdouble
Date: Mon, 24 Jan 2022 18:30:13 +0000	[thread overview]
Message-ID: <bug-104208-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104208
           Summary: -mlong-double-64 should override a previous
                    -mabi=ibmlongdouble
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: fw at gcc dot gnu.org
  Target Milestone: ---
             Build: powerpc64le-*-linux-gnu

We have trouble building glibc 2.35 with GCC 12 because -mlong-double-64 and
-mabi=ibmlongdouble conflict:

ppc64le: gcc 12 vs -mabi=ibmlongdouble
https://sourceware.org/pipermail/libc-alpha/2022-January/135647.html

glibc needs to build itself with -mabi=ibmlongdouble because that's how the
source tree defaults are laid out, and given our build system, it's very
difficult to remove that for individual files. So I'd appreciate a GCC-side fix
for this.

             reply	other threads:[~2022-01-24 18:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 18:30 fw at gcc dot gnu.org [this message]
2022-01-24 18:30 ` [Bug target/104208] " fw at gcc dot gnu.org
2022-02-28 20:08 ` segher at gcc dot gnu.org
2022-03-01 22:55 ` bergner at gcc dot gnu.org
2022-03-01 23:16 ` jakub at gcc dot gnu.org
2022-03-02  0:37 ` bergner at gcc dot gnu.org
2022-03-02  8:23 ` jakub at gcc dot gnu.org
2022-03-02 17:56 ` bergner at gcc dot gnu.org
2022-03-02 18:08 ` fw at gcc dot gnu.org
2022-03-04  6:16 ` bergner at gcc dot gnu.org
2022-03-04 15:04 ` cvs-commit at gcc dot gnu.org
2022-03-04 23:43 ` bergner at gcc dot gnu.org
2022-03-05  2:11 ` bergner at gcc dot gnu.org
2022-03-11 11:35 ` fw at gcc dot gnu.org
2022-03-18 19:10 ` cvs-commit at gcc dot gnu.org
2022-03-18 19:10 ` cvs-commit at gcc dot gnu.org
2022-03-18 19:21 ` bergner 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-104208-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).