public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug testsuite/94763] New: UNRESOLVED scan assembler tests on arm-none-eabi
@ 2020-04-25 18:48 vvinayag at arm dot com
2020-04-26 8:55 ` [Bug testsuite/94763] " clyon at gcc dot gnu.org
` (4 more replies)
0 siblings, 5 replies; 6+ messages in thread
From: vvinayag at arm dot com @ 2020-04-25 18:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
Bug ID: 94763
Summary: UNRESOLVED scan assembler tests on arm-none-eabi
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: vvinayag at arm dot com
Target Milestone: ---
Many tests are UNRESOLVED on arm-none-eabi.
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++14 scan-assembler _Z1fB3barB3fooi
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++14 scan-assembler
_Z1gB3baz1AB3bar
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++17 scan-assembler _Z1fB3barB3fooi
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++17 scan-assembler
_Z1gB3baz1AB3bar
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++2a scan-assembler _Z1fB3barB3fooi
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++2a scan-assembler
_Z1gB3baz1AB3bar
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++98 scan-assembler _Z1fB3barB3fooi
UNRESOLVED: g++.dg/abi/abi-tag1.C -std=gnu++98 scan-assembler
_Z1gB3baz1AB3bar
UNRESOLVED: g++.dg/abi/abi-tag10.C -std=c++14 scan-assembler
_ZNK4hashI12basic_stringB5cxx11Ic11char_traitsIcE9allocatorIcEEEclES5_
UNRESOLVED: g++.dg/abi/abi-tag10.C -std=c++17 scan-assembler
_ZNK4hashI12basic_stringB5cxx11Ic11char_traitsIcE9allocatorIcEEEclES5_
UNRESOLVED: g++.dg/abi/abi-tag10.C -std=c++2a scan-assembler
_ZNK4hashI12basic_stringB5cxx11Ic11char_traitsIcE9allocatorIcEEEclES5_
UNRESOLVED: g++.dg/abi/abi-tag10.C -std=c++98 scan-assembler
_ZNK4hashI12basic_stringB5cxx11Ic11char_traitsIcE9allocatorIcEEEclES5_
UNRESOLVED: g++.dg/abi/abi-tag11.C -std=c++14 scan-assembler
_Z1fSbB3fooIwSt11char_traitsIwESaIwEES3_
UNRESOLVED: g++.dg/abi/abi-tag11.C -std=c++17 scan-assembler
_Z1fSbB3fooIwSt11char_traitsIwESaIwEES3_
UNRESOLVED: g++.dg/abi/abi-tag11.C -std=c++2a scan-assembler
_Z1fSbB3fooIwSt11char_traitsIwESaIwEES3_
UNRESOLVED: g++.dg/abi/abi-tag11.C -std=c++98 scan-assembler
_Z1fSbB3fooIwSt11char_traitsIwESaIwEES3_
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++14 scan-assembler _Z1aB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++14 scan-assembler _Z1fB5cxx11v
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++14 scan-assembler
_Z1fPN7__cxx111AE
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++14 scan-assembler
_Z1gIN7__cxx111AEET_v
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++14 scan-assembler
_Z1vIN7__cxx111AEE
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++17 scan-assembler _Z1aB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++17 scan-assembler _Z1fB5cxx11v
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++17 scan-assembler
_Z1fPN7__cxx111AE
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++17 scan-assembler
_Z1gIN7__cxx111AEET_v
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++17 scan-assembler
_Z1vIN7__cxx111AEE
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++2a scan-assembler _Z1aB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++2a scan-assembler _Z1fB5cxx11v
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++2a scan-assembler
_Z1fPN7__cxx111AE
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++2a scan-assembler
_Z1gIN7__cxx111AEET_v
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++2a scan-assembler
_Z1vIN7__cxx111AEE
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++98 scan-assembler _Z1aB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++98 scan-assembler _Z1fB5cxx11v
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++98 scan-assembler
_Z1fPN7__cxx111AE
UNRESOLVED: g++.dg/abi/abi-tag14.C -std=gnu++98 scan-assembler
_Z1gIN7__cxx111AEET_v
UNRESOLVED: g++.dg/abi/abi-tag16.C -std=gnu++14 scan-assembler
_ZGVZN1N1FEvE4NameB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag16.C -std=gnu++17 scan-assembler
_ZGVZN1N1FEvE4NameB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag16.C -std=gnu++2a scan-assembler
_ZGVZN1N1FEvE4NameB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag16.C -std=gnu++98 scan-assembler
_ZGVZN1N1FEvE4NameB5cxx11
UNRESOLVED: g++.dg/abi/abi-tag16a.C -std=gnu++14 scan-assembler
_ZGVZN1N1FEvE4Name
UNRESOLVED: g++.dg/abi/abi-tag16a.C -std=gnu++17 scan-assembler
_ZGVZN1N1FEvE4Name
UNRESOLVED: g++.dg/abi/abi-tag16a.C -std=gnu++2a scan-assembler
_ZGVZN1N1FEvE4Name
UNRESOLVED: g++.dg/abi/abi-tag16a.C -std=gnu++98 scan-assembler
_ZGVZN1N1FEvE4Name
UNRESOLVED: g++.dg/abi/abi-tag17.C -std=c++14 scan-assembler _Z3fi1B6_X_tagv
UNRESOLVED: g++.dg/abi/abi-tag17.C -std=c++17 scan-assembler _Z3fi1B6_X_tagv
UNRESOLVED: g++.dg/abi/abi-tag17.C -std=c++2a scan-assembler _Z3fi1B6_X_tagv
UNRESOLVED: g++.dg/abi/abi-tag17.C -std=c++98 scan-assembler _Z3fi1B6_X_tagv
UNRESOLVED: g++.dg/template/friend56.C -std=c++14 scan-assembler _Z1fv
UNRESOLVED: g++.dg/template/friend56.C -std=c++17 scan-assembler _Z1fv
UNRESOLVED: g++.dg/template/friend56.C -std=c++2a scan-assembler _Z1fv
UNRESOLVED: g++.dg/template/friend56.C -std=c++98 scan-assembler _Z1fv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++14 scan-assembler
(weak|glob)[^\n]*_Z3fooIXadL_Z13external_funcvEEEvv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++14 scan-assembler-not
(weak|glob)[^\n]*_Z3fooIXadL_ZL11static_funcvEEEvv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++17 scan-assembler
(weak|glob)[^\n]*_Z3fooIXadL_Z13external_funcvEEEvv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++17 scan-assembler-not
(weak|glob)[^\n]*_Z3fooIXadL_ZL11static_funcvEEEvv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++2a scan-assembler
(weak|glob)[^\n]*_Z3fooIXadL_Z13external_funcvEEEvv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++2a scan-assembler-not
(weak|glob)[^\n]*_Z3fooIXadL_ZL11static_funcvEEEvv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++98 scan-assembler
(weak|glob)[^\n]*_Z3fooIXadL_Z13external_funcvEEEvv
UNRESOLVED: g++.dg/template/linkage1.C -std=c++98 scan-assembler-not
(weak|glob)[^\n]*_Z3fooIXadL_ZL11static_funcvEEEvv
UNRESOLVED: g++.dg/template/spec38.C -std=c++14 scan-assembler _Z1fIiEvPT_
UNRESOLVED: g++.dg/template/spec38.C -std=c++17 scan-assembler _Z1fIiEvPT_
UNRESOLVED: g++.dg/template/spec38.C -std=c++2a scan-assembler _Z1fIiEvPT_
UNRESOLVED: g++.dg/template/spec38.C -std=c++98 scan-assembler _Z1fIiEvPT_
UNRESOLVED: g++.dg/template/static26.C -std=c++14 scan-assembler-not computed
UNRESOLVED: g++.dg/template/static26.C -std=c++17 scan-assembler-not computed
UNRESOLVED: g++.dg/template/static26.C -std=c++2a scan-assembler-not computed
UNRESOLVED: g++.dg/template/static26.C -std=c++98 scan-assembler-not computed
UNRESOLVED: g++.dg/tls/static2.C -std=c++14 scan-assembler-not _ZTHN1A1iE
UNRESOLVED: g++.dg/tls/static2.C -std=c++14 scan-assembler-not _ZTWN1A1iE
UNRESOLVED: g++.dg/tls/static2.C -std=c++17 scan-assembler-not _ZTHN1A1iE
UNRESOLVED: g++.dg/tls/static2.C -std=c++17 scan-assembler-not _ZTWN1A1iE
UNRESOLVED: g++.dg/tls/static2.C -std=c++2a scan-assembler-not _ZTHN1A1iE
UNRESOLVED: g++.dg/tls/static2.C -std=c++2a scan-assembler-not _ZTWN1A1iE
UNRESOLVED: g++.dg/tls/static2.C -std=c++98 scan-assembler-not _ZTHN1A1iE
UNRESOLVED: g++.dg/tls/static2.C -std=c++98 scan-assembler-not _ZTWN1A1iE
... and many more tests.
The UNRESOLVED tests seem to have started between GCC commit
f84aded848f6fdd2704c9376263c6d1aee6bb0ca and
89b01e86ff8521a0decf292595089e5631cc9320.
Looking at the g++.log file, it seems that the -S flag is missing from the
command-line options, and therefore an assembler file is not output, and
therefore resulting in UNRESOLVED test. I am investigating further.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/94763] UNRESOLVED scan assembler tests on arm-none-eabi
2020-04-25 18:48 [Bug testsuite/94763] New: UNRESOLVED scan assembler tests on arm-none-eabi vvinayag at arm dot com
@ 2020-04-26 8:55 ` clyon at gcc dot gnu.org
2020-04-27 10:56 ` rearnsha at gcc dot gnu.org
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: clyon at gcc dot gnu.org @ 2020-04-26 8:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
--- Comment #1 from Christophe Lyon <clyon at gcc dot gnu.org> ---
How do you configure GCC, and what flags to you use to run the tests?
They work for me, on several configuration of arm-non-eabi-gcc as
cross-compiler.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/94763] UNRESOLVED scan assembler tests on arm-none-eabi
2020-04-25 18:48 [Bug testsuite/94763] New: UNRESOLVED scan assembler tests on arm-none-eabi vvinayag at arm dot com
2020-04-26 8:55 ` [Bug testsuite/94763] " clyon at gcc dot gnu.org
@ 2020-04-27 10:56 ` rearnsha at gcc dot gnu.org
2020-04-29 15:48 ` vvinayag at arm dot com
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: rearnsha at gcc dot gnu.org @ 2020-04-27 10:56 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2020-04-27
Status|UNCONFIRMED |WAITING
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/94763] UNRESOLVED scan assembler tests on arm-none-eabi
2020-04-25 18:48 [Bug testsuite/94763] New: UNRESOLVED scan assembler tests on arm-none-eabi vvinayag at arm dot com
2020-04-26 8:55 ` [Bug testsuite/94763] " clyon at gcc dot gnu.org
2020-04-27 10:56 ` rearnsha at gcc dot gnu.org
@ 2020-04-29 15:48 ` vvinayag at arm dot com
2020-04-30 8:52 ` clyon at gcc dot gnu.org
2020-04-30 16:17 ` vvinayag at arm dot com
4 siblings, 0 replies; 6+ messages in thread
From: vvinayag at arm dot com @ 2020-04-29 15:48 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
--- Comment #2 from vvinayag at arm dot com ---
(In reply to Christophe Lyon from comment #1)
> How do you configure GCC, and what flags to you use to run the tests?
> They work for me, on several configuration of arm-non-eabi-gcc as
> cross-compiler.
Sorry for the late reply.
The tests appear to pass when I invoke them locally. They only failed as part
of our buildbot run tests. It could be a glitch in our test system. But I was
wondering whether there were any recent changes in the testsuites.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/94763] UNRESOLVED scan assembler tests on arm-none-eabi
2020-04-25 18:48 [Bug testsuite/94763] New: UNRESOLVED scan assembler tests on arm-none-eabi vvinayag at arm dot com
` (2 preceding siblings ...)
2020-04-29 15:48 ` vvinayag at arm dot com
@ 2020-04-30 8:52 ` clyon at gcc dot gnu.org
2020-04-30 16:17 ` vvinayag at arm dot com
4 siblings, 0 replies; 6+ messages in thread
From: clyon at gcc dot gnu.org @ 2020-04-30 8:52 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
--- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
(In reply to vvinayag from comment #2)
> Sorry for the late reply.
> The tests appear to pass when I invoke them locally. They only failed as
> part of our buildbot run tests. It could be a glitch in our test system. But
> I was wondering whether there were any recent changes in the testsuites.
If you still have the .log file, you could check why the tests are UNRESOLVED,
there's probably an error message nearby.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug testsuite/94763] UNRESOLVED scan assembler tests on arm-none-eabi
2020-04-25 18:48 [Bug testsuite/94763] New: UNRESOLVED scan assembler tests on arm-none-eabi vvinayag at arm dot com
` (3 preceding siblings ...)
2020-04-30 8:52 ` clyon at gcc dot gnu.org
@ 2020-04-30 16:17 ` vvinayag at arm dot com
4 siblings, 0 replies; 6+ messages in thread
From: vvinayag at arm dot com @ 2020-04-30 16:17 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94763
vvinayag at arm dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from vvinayag at arm dot com ---
(In reply to Christophe Lyon from comment #3)
> (In reply to vvinayag from comment #2)
>
> > Sorry for the late reply.
> > The tests appear to pass when I invoke them locally. They only failed as
> > part of our buildbot run tests. It could be a glitch in our test system. But
> > I was wondering whether there were any recent changes in the testsuites.
>
> If you still have the .log file, you could check why the tests are
> UNRESOLVED, there's probably an error message nearby.
Thanks Christophe.
I am going to close this as this is not present in the latest build. I will
keep a lookout in case this happens again.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-04-30 16:17 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-25 18:48 [Bug testsuite/94763] New: UNRESOLVED scan assembler tests on arm-none-eabi vvinayag at arm dot com
2020-04-26 8:55 ` [Bug testsuite/94763] " clyon at gcc dot gnu.org
2020-04-27 10:56 ` rearnsha at gcc dot gnu.org
2020-04-29 15:48 ` vvinayag at arm dot com
2020-04-30 8:52 ` clyon at gcc dot gnu.org
2020-04-30 16:17 ` vvinayag at arm dot com
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).