public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/47334] g++.dg/torture/pr31863.C -O2 -flto FAILs without visibility Date: Wed, 27 Nov 2013 13:20:00 -0000 [thread overview] Message-ID: <bug-47334-4-KXxfxivbn8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47334-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47334 --- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- This issue now causes new failures on Solaris 9 with Sun as: FAIL: gcc.dg/atomic/c11-atomic-exec-1.c -O2 -flto (test for excess errors) Excess errors: /vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.dg/atomic/c11-atomic-exec-1.c:81:1 : warning: visibility attribute not supported in this configuration; ignored [-W attributes] lto1: warning: visibility attribute not supported in this configuration; ignored [-Wattributes] FAIL: gcc.dg/atomic/c11-atomic-exec-2.c -O2 -flto (test for excess errors) FAIL: gcc.dg/atomic/c11-atomic-exec-3.c -O2 -flto (test for excess errors) FAIL: gcc.dg/atomic/c11-atomic-exec-4.c -O2 -flto (test for excess errors) Rainer
next prev parent reply other threads:[~2013-11-27 13:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-17 18:13 [Bug lto/47334] New: " ro at gcc dot gnu.org 2011-03-23 12:58 ` [Bug lto/47334] " ro at gcc dot gnu.org 2011-03-23 13:02 ` rguenther at suse dot de 2011-04-28 16:27 ` rguenth at gcc dot gnu.org 2013-11-27 13:20 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2021-12-24 8:36 ` [Bug middle-end/47334] " pinskia at gcc dot gnu.org 2021-12-26 1:52 ` pinskia at gcc dot gnu.org 2021-12-29 19:27 ` [Bug testsuite/47334] " fxcoudert at gcc dot gnu.org 2023-01-06 9:17 ` cvs-commit at gcc dot gnu.org 2023-01-06 9:35 ` cvs-commit 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-47334-4-KXxfxivbn8@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).