public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Reid Wahl via Gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
Date: Mon, 22 Aug 2022 10:41:03 +0200	[thread overview]
Message-ID: <87o7wc4qn4.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAPiuu9_=ZtFZUD+3+vzKUuvShxWezf1ngjnm0=dUmDNBQwiShg@mail.gmail.com> (Reid Wahl via Gcc-help's message of "Sun, 21 Aug 2022 19:39:40 -0700")

* Reid Wahl via Gcc-help:

> I have no idea what's causing the unit test to fail on Fedora 36 Power
> 9 LE (the only system in the test bed that's still failing), but I
> don't have a reproducer or enough information to ask a question. I'll
> try to get one set up this week and go from there.

The POWER failure could be related to the float128 redirects.  The
snprintf symbol is necessarily different there as well
(__snprintfieee128).  This is completely unrelated to fortification.

I must say I do not find it particularly helpful to label this as
off-topic on the gcc-help list.  Source foritification is a feature that
sits between GCC and glibc.  GCC is very much aware of what the chk
variants do.

Thanks,
Florian


  parent reply	other threads:[~2022-08-22  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22  0:53 Reid Wahl
2022-08-22  2:39 ` Reid Wahl
2022-08-22  3:03   ` Xi Ruoyao
2022-08-22  4:07     ` Reid Wahl
2022-08-22  8:41   ` Florian Weimer [this message]
2022-08-22  8:54     ` Reid Wahl

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=87o7wc4qn4.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gcc-help@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).