public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31286] glibc 2.36: Aliasing violation in libio/iovdprintf.c before refactor to internal buffers
Date: Thu, 15 Feb 2024 18:16:08 +0000	[thread overview]
Message-ID: <bug-31286-131-Aen20xnPGB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31286-131@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Sam James <sam at gentoo dot org> ---
-Wstrict-aliasing=2 has many complaints as well with gcc version 14.0.1
20240214 (experimental) and -O3. I don't think all of them are real problems,
but at a glance, at least some of them are.

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

      parent reply	other threads:[~2024-02-15 18:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  4:27 [Bug libc/31286] New: " carlos at redhat dot com
2024-01-25 10:47 ` [Bug libc/31286] " sam at gentoo dot org
2024-01-25 12:32 ` carlos at redhat dot com
2024-01-25 16:52 ` fweimer at redhat dot com
2024-02-15 18:16 ` sam at gentoo dot org [this message]

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-31286-131-Aen20xnPGB@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).