public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug stdio/26690] Aliasing violation in __vfscanf_internal Date: Tue, 06 Oct 2020 09:56:07 +0000 [thread overview] Message-ID: <bug-26690-131-6abOkZ4tgV@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26690-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26690 Szabolcs Nagy <nsz at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nsz at gcc dot gnu.org --- Comment #3 from Szabolcs Nagy <nsz at gcc dot gnu.org> --- i'm seeing this on aarch64 too: crypt/cert test case does not finish reading the input and fills up the disk: $ ./testrun.sh crypt/cert < $glibcsrc/crypt/cert.input K: 0000000000000000 P: 0000000000000000 C: 0000000000000000 Encrypt FAIL K: 0000000000000000 P: 0000000000000000 C: 0000000000000000 Encrypt FAIL K: 0000000000000000 P: 0000000000000000 C: 0000000000000000 Encrypt FAIL K: 0000000000000000 P: 0000000000000000 C: 0000000000000000 Encrypt FAIL K: 0000000000000000 P: 0000000000000000 C: 0000000000000000 Encrypt FAIL ... a cut down test case: #include <stdio.h> int main() { int r,t; r = sscanf("01", "%2x", &t); printf("scanf: %d %02x\n", r, t); return 0; } with new gcc it prints scanf: 0 00 with the patch from #c2 i get the expected scanf: 1 01 -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-06 9:56 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-01 11:53 [Bug stdio/26690] New: " schwab@linux-m68k.org 2020-10-01 11:55 ` [Bug stdio/26690] " schwab@linux-m68k.org 2020-10-01 21:41 ` slyfox at inbox dot ru 2020-10-06 9:56 ` nsz at gcc dot gnu.org [this message] 2020-10-07 18:43 ` tuliom at ascii dot art.br 2020-10-08 8:16 ` schwab@linux-m68k.org 2020-10-08 17:36 ` slyfox at inbox dot ru
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-26690-131-6abOkZ4tgV@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: 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).