public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/66723] New: gcc.target/i386/vararg-loc.c FAILs
@ 2015-07-01 14:23 ro at gcc dot gnu.org
  2015-07-01 14:24 ` [Bug tree-optimization/66723] " ro at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: ro at gcc dot gnu.org @ 2015-07-01 14:23 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66723

            Bug ID: 66723
           Summary: gcc.target/i386/vararg-loc.c FAILs
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ro at gcc dot gnu.org
                CC: vries at gcc dot gnu.org
  Target Milestone: ---
              Host: i386-pc-solaris2.1[01], x86_64-apple-darwin*
            Target: i386-pc-solaris2.1[01], x86_64-apple-darwin*
             Build: i386-pc-solaris2.1[01], x86_64-apple-darwin*

The new gcc.target/i386/vararg-loc.c FAILs on Solaris/x86 when configured to
used
/usr/ccs/bin/as, and Mac OS X with the native assembler:

FAIL: gcc.target/i386/vararg-loc.c scan-assembler-times \\\\.loc 1 18 0 1
FAIL: gcc.target/i386/vararg-loc.c scan-assembler-times \\\\.loc 1 20 0 1

.loc support seems to be a gas-only feature, currently.

  Rainer


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2015-07-01 17:47 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-07-01 14:23 [Bug tree-optimization/66723] New: gcc.target/i386/vararg-loc.c FAILs ro at gcc dot gnu.org
2015-07-01 14:24 ` [Bug tree-optimization/66723] " ro at gcc dot gnu.org
2015-07-01 17:33 ` [Bug testsuite/66723] " vries at gcc dot gnu.org
2015-07-01 17:46 ` vries at gcc dot gnu.org
2015-07-01 17:47 ` vries at gcc dot gnu.org

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).