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 target/59407] New: gcc.target/i386/pr58218.c FAILs with Sun as
Date: Fri, 06 Dec 2013 13:39:00 -0000 [thread overview]
Message-ID: <bug-59407-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59407
Bug ID: 59407
Summary: gcc.target/i386/pr58218.c FAILs with Sun as
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ubizjak at gmail dot com
Host: i386-pc-solaris2.1[01]
Target: i386-pc-solaris2.1[01]
Build: i386-pc-solaris2.1[01]
The new gcc.target/i386/pr58218.c testcase FAILs on Solaris 10 and 11/x86 with
Sun as:
FAIL: gcc.target/i386/pr58218.c (test for excess errors)
Excess errors:
Assembler: pr58218.c
"/var/tmp//cciHFIO7.s", line 3 : Section attributes do not match
as chokes on
.section .lbss,"aw",@nobits
It turns out that as needs an explicit 'h' (for huge or large) flag here to set
SHF_AMD64_LARGE.
gas doesn't need that (sets SHF_AMD64_LARGE implicitly for the .l* sections
prescribed by the AMD64 ABI to have that), but accepts an 'l' flag with the
same semantics as 'h' here.
Will look into how to get this into gcc.
Rainer
next reply other threads:[~2013-12-06 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 13:39 ro at gcc dot gnu.org [this message]
2013-12-06 13:39 ` [Bug target/59407] " ro at gcc dot gnu.org
2014-04-22 11:38 ` jakub at gcc dot gnu.org
2014-07-16 13:29 ` jakub at gcc dot gnu.org
2014-10-30 10:43 ` jakub at gcc dot gnu.org
2014-12-10 15:13 ` rguenth 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-59407-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: 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).