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 lto/94157] [10 Regression] error: lto-wrapper failed with -Wa,--noexecstack -Wa,--noexecstack since r10-6807-gf1a681a174cdfb82
Date: Sun, 15 Mar 2020 13:25:19 +0000 [thread overview]
Message-ID: <bug-94157-4-ug1gFY6ynK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94157-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94157
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |ro at gcc dot gnu.org
Resolution|FIXED |---
--- Comment #6 from Rainer Orth <ro at gcc dot gnu.org> ---
The new test FAILs on (at least) Solaris with the native assembler (and
probably
others like Darwin and HP-UX):
+FAIL: gcc.dg/lto/pr94157 c_lto_pr94157_0.o assemble, -O0 -fipa-vrp -flto
-Wa,--noexecstack -Wa,--noexecstack -Wa,--execstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack
+UNRESOLVED: gcc.dg/lto/pr94157 c_lto_pr94157_0.o-c_lto_pr94157_0.o execute
-O0 -fipa-vrp -flto -Wa,--noexecstack -Wa,--noexecstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack
+UNRESOLVED: gcc.dg/lto/pr94157 c_lto_pr94157_0.o-c_lto_pr94157_0.o link -O0
-fipa-vrp -flto -Wa,--noexecstack -Wa,--noexecstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack -Wa,--execstack
-Wa,--execstack -Wa,--execstack -Wa,--execstack
/usr/ccs/bin/as: error: unknown option '-'^M
/usr/ccs/bin/as: error: unknown option '-'^M
/usr/ccs/bin/as: error: unknown option 'e'^M
/usr/ccs/bin/as: error: unknown option 'xecstack'^M
/usr/ccs/bin/as: error: unknown option '-'^M
/usr/ccs/bin/as: error: unknown option 'e'^M
/usr/ccs/bin/as: error: unknown option 'xecstack'^M
[...]
Either use something portable here or restrict the test to assemblers supporing
--execstack/--noexecstack.
next prev parent reply other threads:[~2020-03-15 13:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 18:28 [Bug lto/94157] New: [10 Regression] error: lto-wrapper failed with -Wa,--noexecstack -Wa,--noexecstack marxin at gcc dot gnu.org
2020-03-12 18:33 ` [Bug lto/94157] " marxin at gcc dot gnu.org
2020-03-12 18:36 ` [Bug lto/94157] [10 Regression] error: lto-wrapper failed with -Wa,--noexecstack -Wa,--noexecstack since r10-6807-gf1a681a174cdfb82 marxin at gcc dot gnu.org
2020-03-12 18:38 ` marxin at gcc dot gnu.org
2020-03-12 18:50 ` marxin at gcc dot gnu.org
2020-03-12 18:57 ` prathamesh3492 at gcc dot gnu.org
2020-03-13 12:51 ` marxin at gcc dot gnu.org
2020-03-15 13:25 ` ro at gcc dot gnu.org [this message]
2020-03-17 8:45 ` cvs-commit at gcc dot gnu.org
2020-03-17 8:47 ` marxin at gcc dot gnu.org
2022-04-22 9:30 ` jiawei at iscas dot ac.cn
2022-04-22 11:36 ` marxin at gcc dot gnu.org
2022-04-24 1:45 ` jiawei at iscas dot ac.cn
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-94157-4-ug1gFY6ynK@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: link
Be 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).