public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17836] [4.0 Regression] ABI breakage for 16-byte vectors (non-Altivec ABI & ISA) Date: Wed, 14 Jan 2015 21:51:00 -0000 [thread overview] Message-ID: <bug-17836-4-lEHmHuPXJP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-17836-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17836 --- Comment #7 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> --- Author: hjl Date: Wed Jan 14 21:51:09 2015 New Revision: 219616 URL: https://gcc.gnu.org/viewcvs?rev=219616&root=gcc&view=rev Log: Correct target selector in -mfentry tests -fprofile -mfentry works with PIE if gcrt1.o is compiled with -fPIC. A glibc has been filed, PR 17836, and a glibc patch has been submitted. * gcc.target/i386/fentry-override.c: Properly place {} in target selector. Remove nonpic. * gcc.target/i386/fentry.c: Likewise. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.target/i386/fentry-override.c trunk/gcc/testsuite/gcc.target/i386/fentry.c
next parent reply other threads:[~2015-01-14 21:51 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-17836-4@http.gcc.gnu.org/bugzilla/> 2015-01-14 21:51 ` hjl at gcc dot gnu.org [this message] 2004-10-05 7:49 [Bug target/17836] New: " bonzini at gcc dot gnu dot org 2004-10-05 7:49 ` [Bug target/17836] " bonzini at gcc dot gnu dot org 2004-10-07 16:23 ` pinskia at gcc dot gnu dot org 2004-10-08 7:18 ` bonzini at gcc dot gnu dot org 2004-10-10 20:27 ` pinskia at gcc dot gnu dot org 2004-10-11 7:18 ` paolo dot bonzini at polimi dot it 2004-11-22 1:21 ` cvs-commit at gcc dot gnu dot org 2004-11-23 1:33 ` dje at gcc dot gnu dot org 2004-11-23 8:20 ` paolo dot bonzini at lu dot unisi dot ch
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-17836-4-lEHmHuPXJP@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).