public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Aldy Hernandez <aldyh@redhat.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] range-op: Implement floating point division fold_range [PR107569]
Date: Tue, 22 Nov 2022 22:58:43 +0000	[thread overview]
Message-ID: <b6bd3390-3d73-e9f-dc39-e47f4516eaff@codesourcery.com> (raw)
In-Reply-To: <20221122074117.d6632jj7kkmunwh4@lug-owl.de>

On Tue, 22 Nov 2022, Jan-Benedict Glaw wrote:

> I'm running a slightly hacked [glibc]/scripts/build-many-glibcs.py to
> to CI builds for glibc as well by now (hacked to allow for GCC master
> being used) and this GCC commit
> (2d5c4a16dd833aa083f13dd3e78e3ef38afe6ebb) triggers glibc's
> elf/check-localplt testcase to fail, though just for
> sparc64-linux-gnu. (As I just started with glibc checks, it took me a
> while to realize this was a real regression and not a flaw in my
> setup.)

I think the appropriate fix is to update the relevant localplt.data (to 
add the relevant libgcc symbol marked with "?" as optional), I don't think 
there's a GCC bug here.

-- 
Joseph S. Myers
joseph@codesourcery.com

  reply	other threads:[~2022-11-22 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  9:09 Jakub Jelinek
2022-11-22  7:41 ` Jan-Benedict Glaw
2022-11-22 22:58   ` Joseph Myers [this message]
2022-11-30 10:04 ` Iain Buclaw

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=b6bd3390-3d73-e9f-dc39-e47f4516eaff@codesourcery.com \
    --to=joseph@codesourcery.com \
    --cc=aldyh@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jbglaw@lug-owl.de \
    /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).