public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/61949] New: [4.10 regression] SEGV compiling gcc.dg/pch/import-[12].c Date: Tue, 29 Jul 2014 15:10:00 -0000 [thread overview] Message-ID: <bug-61949-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61949 Bug ID: 61949 Summary: [4.10 regression] SEGV compiling gcc.dg/pch/import-[12].c Product: gcc Version: 4.10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: ro at gcc dot gnu.org CC: rguenth at gcc dot gnu.org Host: i386-pc-solaris2.10 Target: i386-pc-solaris2.10 Build: i386-pc-solaris2.10 Between 20140711 (r212451) and 20140718 (r15669), the gcc.dg/pch/import-[12].c tests started to FAIL on Solaris 10/x86 (only, Solaris 11 is unaffected): FAIL: gcc.dg/pch/import-1.c -O0 -g -I. -Dwith_PCH (internal compiler error) FAIL: gcc.dg/pch/import-1.c -O0 -g -I. -Dwith_PCH (test for excess errors) FAIL: gcc.dg/pch/import-1.c -O0 -g assembly comparison and all others, both 32 and 64-bit. cc1 SEGVs here: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1 (LWP 1)] 0x08c34226 in md5_read_ctx (resbuf=0x8047278, ctx=0x8047140) at /vol/gcc/src/hg/trunk/local/libiberty/md5.c:91 91 memcpy (resbuf, buffer, 16); 1: x/i $pc => 0x8c34226 <md5_finish_ctx+150>: movaps -0x28(%ebp),%xmm0 -0x28(%ebp) isn't 16-byte aligned as required. This only happens with the stage3 cc1, stages 1 and 2 are unaffected. A reghunt revealed that this is caused by this patch: 2014-07-11 Richard Biener <rguenther@suse.de> PR middle-end/61473 * builtins.c (fold_builtin_memory_op): Inline memory moves that can be implemented with a single load followed by a single store. (c_strlen): Only warn when only_value is not 2. Rainer
next reply other threads:[~2014-07-29 15:10 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-07-29 15:10 ro at gcc dot gnu.org [this message] 2014-07-29 15:10 ` [Bug middle-end/61949] " ro at gcc dot gnu.org 2014-07-30 10:01 ` rguenth at gcc dot gnu.org 2014-07-30 12:14 ` ro at gcc dot gnu.org 2014-07-30 12:14 ` ro at CeBiTec dot Uni-Bielefeld.DE 2014-07-30 14:07 ` [Bug target/61949] " rguenth at gcc dot gnu.org 2014-07-30 14:54 ` hjl.tools at gmail dot com 2015-02-17 18:58 ` [Bug target/61949] [5 " jakub at gcc dot gnu.org 2015-02-19 14:33 ` jakub 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-61949-4@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).