public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/29452] /home/dave/gnu/glibc/glibc/debug/../string/bits/string_fortified.h:30: undefined  reference to `__builtin_dynamic_object_size'
Date: Mon, 08 Aug 2022 16:11:21 +0000	[thread overview]
Message-ID: <bug-29452-131-YX1lgI5TM5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29452-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29452

--- Comment #3 from dave.anglin at bell dot net ---
On 2022-08-07 4:43 a.m., fweimer at redhat dot com wrote:
> --- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
> (In reply to John David Anglin from comment #0)
>> gcc version 12.0.0 20211008 (experimental) [master r13-1220-g7c1c7e120cc]
>> (GCC)
> That looks like a GCC snapshot that's just too old. The version-based header
> conditionals work only with released compilers (and later stage 4 snapshots
> because of the development wind-down).
Shouldn't the prereq for __builtin_dynamic_object_size be GCC 12.1 instead of
12.0?

There's no 12.0 release and the feature was added during the development phase
for the
first GCC 12 release.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-08-08 16:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 14:41 [Bug string/29452] New: " danglin at gcc dot gnu.org
2022-08-07  8:43 ` [Bug string/29452] " fweimer at redhat dot com
2022-08-07 15:07 ` dave.anglin at bell dot net
2022-08-08 16:11 ` dave.anglin at bell dot net [this message]
2022-08-08 16:19 ` siddhesh at sourceware dot org
2023-07-07 15:03 ` fernando.hueso at uv dot es
2023-07-07 15:08 ` siddhesh at sourceware dot org
2023-07-07 15:41 ` fernando.hueso at uv dot es

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-29452-131-YX1lgI5TM5@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).