public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/104481] gcc.target/i386/pr35513-8.c and g++.target/i386/pr35513-[12].C testsuire failures
Date: Thu, 10 Feb 2022 08:39:51 +0000	[thread overview]
Message-ID: <bug-104481-4-VZwG0I3J0I@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104481-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
spawn -ignore SIGHUP /hdd/uros/gcc-build-fast/gcc/xgcc
-B/hdd/uros/gcc-build-fast/gcc/ -fdiagnostics-plain-output -mx32 -O2 -fno-pic
-fexceptions -fasynchronous-unwind-tables -mno-direct-extern-access
-ffat-lto-objects -fno-ident -c -o pr35513-8.o
/hdd/uros/git/gcc/gcc/testsuite/gcc.target/i386/pr35513-8.c
PASS: gcc.target/i386/pr35513-8.c (test for excess errors)
gcc.target/i386/pr35513-8.c: output file does not exist
UNRESOLVED: gcc.target/i386/pr35513-8.c scan-assembler .section[
\t]+.note.gnu.property,
gcc.target/i386/pr35513-8.c: output file does not exist
UNRESOLVED: gcc.target/i386/pr35513-8.c scan-assembler .long[ \t]+0xb0008000

and:

spawn -ignore SIGHUP /hdd/uros/gcc-build-fast/gcc/testsuite/g++/../../xg++
-B/hdd/uros/gcc-build-fast/gcc/testsuite/g++/../../
/hdd/uros/git/gcc/gcc/testsuite/g++.target/i386/pr35513-1.C
-fdiagnostics-plain-output -nostdinc++
-I/hdd/uros/gcc-build-fast/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/hdd/uros/gcc-build-fast/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/hdd/uros/git/gcc/libstdc++-v3/libsupc++
-I/hdd/uros/git/gcc/libstdc++-v3/include/backward
-I/hdd/uros/git/gcc/libstdc++-v3/testsuite/util -fmessage-length=0 -std=gnu++98
-O2 -mno-direct-extern-access
-L/hdd/uros/gcc-build-fast/x86_64-pc-linux-gnu/./libstdc++-v3/src/.libs
-B/hdd/uros/gcc-build-fast/x86_64-pc-linux-gnu/./libstdc++-v3/src/.libs
-L/hdd/uros/gcc-build-fast/x86_64-pc-linux-gnu/./libstdc++-v3/src/.libs
-B/hdd/uros/gcc-build-fast/x86_64-pc-linux-gnu/./libitm/
-L/hdd/uros/gcc-build-fast/x86_64-pc-linux-gnu/./libitm/.libs -lm -o
./pr35513-1.exe
/usr/bin/ld: warning: /tmp/ccW4Yf7H.o: unsupported GNU_PROPERTY_TYPE (5) type:
0xb0008000
FAIL: g++.target/i386/pr35513-1.C  -std=gnu++98 (test for excess errors)
Excess errors:
/usr/bin/ld: warning: /tmp/ccW4Yf7H.o: unsupported GNU_PROPERTY_TYPE (5) type:
0xb0008000

Both on Fedora-33 x86_64.

  parent reply	other threads:[~2022-02-10  8:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  8:29 [Bug testsuite/104481] New: " ubizjak at gmail dot com
2022-02-10  8:31 ` [Bug testsuite/104481] " ubizjak at gmail dot com
2022-02-10  8:39 ` ubizjak at gmail dot com [this message]
2022-02-10  8:41 ` rguenth at gcc dot gnu.org
2022-02-10  8:43 ` ubizjak at gmail dot com
2022-02-10  8:46 ` ubizjak at gmail dot com
2022-02-10  8:50 ` crazylht at gmail dot com
2022-02-10  8:58 ` crazylht at gmail dot com
2022-02-10 13:09 ` hjl.tools at gmail dot com
2022-02-11 14:03 ` hjl.tools at gmail dot com
2022-02-12 13:50 ` cvs-commit at gcc dot gnu.org
2022-02-12 13:51 ` hjl.tools at gmail dot com

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-104481-4-VZwG0I3J0I@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).