public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/97264] [11 Regression] -fpa-modref breaks va_arg on glibc Date: Thu, 01 Oct 2020 09:41:08 +0000 [thread overview] Message-ID: <bug-97264-4-VMHSCI042p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97264-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97264 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsm28 at gcc dot gnu.org, | |rguenth at gcc dot gnu.org Target Milestone|--- |11.0 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- a-t5.c.036t.fre1:ipa-modref: in __vfscanf_internal__/1, call to read_int/0 does not clobber f 2->2 a-t5.c.036t.fre1:ipa-modref: in __vfscanf_internal__/1, call to read_int/0 does not clobber f 2->2 I think this is 'const char *' vs. 'const unsigned char *' being TBAA incompatible. Changing read_int to take 'const char *pstr' fixes things (and changing the type in __vfscanf_internal__ as well). So this seems to be a latent bug in glibc unless somehow C makes those pointers magically compatible wrt TBAA. Joseph?
next prev parent reply other threads:[~2020-10-01 9:41 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-01 8:37 [Bug ipa/97264] New: " slyfox at gcc dot gnu.org 2020-10-01 8:38 ` [Bug ipa/97264] " slyfox at gcc dot gnu.org 2020-10-01 9:41 ` rguenth at gcc dot gnu.org [this message] 2020-10-01 9:50 ` slyfox at gcc dot gnu.org 2020-10-01 9:53 ` rguenther at suse dot de 2020-10-01 10:57 ` schwab@linux-m68k.org 2020-10-01 11:31 ` rguenth at gcc dot gnu.org 2020-10-16 12:09 ` rguenth 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-97264-4-VMHSCI042p@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: linkBe 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).