From: Mark Wielaard <mark@klomp.org>
To: gcc-rust@gcc.gnu.org
Subject: debian-i386 target (Was: ppc64le added to buildbot)
Date: Wed, 2 Jun 2021 00:34:03 +0200 [thread overview]
Message-ID: <YLa12/31P0nqbbNA@wildebeest.org> (raw)
In-Reply-To: <YLVjpnzI6jECZ8sJ@wildebeest.org>
Hi,
On Tue, Jun 01, 2021 at 12:31:02AM +0200, Mark Wielaard wrote:
> There are currently three builders, fedora-x86_64, debian-arm64 and
> fedora-ppc64le which we know are zero fail. It would be nice to see
> how 32bit (debian-i386 or debian-armhf) and big-endian (fedora-s390x
> or fedora-ppc64) targets are doing. I haven't tried them yet.
I tried the simplest 32bit target, debian-i386 and it builds, but make
check-rust fails. It seems to have trouble processing f64
defintions/values.
mark@debian-i386:~/gccrs-build$ gcc/rust1 /home/mark/gccrs/gcc/testsuite/rust.test/compile/methods1.rs
Preparing to parse files.
Attempting to parse file: /home/mark/gccrs/gcc/testsuite/rust.test/compile/methods1.rs
beginning null denotation identifier handling
current peek token when starting path pratt parse: '{'
current token (just about to return path to null denotation): '{'
finished null denotation identifier path parsing - next is branching
values of lookahead: 'identifier' ':' 'float literal' ','
can be struct expr: 'true', not a block: 'true'
struct/enum expr field validated to not be null
struct/enum expr field pushed back
struct/enum expr fields comma skipped
struct/enum expr field validated to not be null
struct/enum expr field pushed back
lack of comma detected in struct/enum expr fields - break
struct/enum expr about to parse struct base
struct/enum expr skipped right curly - done and ready to return
beginning null denotation identifier handling
current peek token when starting path pratt parse: '{'
current token (just about to return path to null denotation): '{'
finished null denotation identifier path parsing - next is branching
values of lookahead: 'identifier' ':' 'identifier' ','
can be struct expr: 'true', not a block: 'true'
beginning null denotation identifier handling
current peek token when starting path pratt parse: ','
current token (just about to return path to null denotation): ','
finished null denotation identifier path parsing - next is branching
struct/enum expr field validated to not be null
struct/enum expr field pushed back
struct/enum expr fields comma skipped
beginning null denotation identifier handling
current peek token when starting path pratt parse: '}'
current token (just about to return path to null denotation): '}'
finished null denotation identifier path parsing - next is branching
struct/enum expr field validated to not be null
struct/enum expr field pushed back
lack of comma detected in struct/enum expr fields - break
struct/enum expr about to parse struct base
struct/enum expr skipped right curly - done and ready to return
successfully parsed inherent impl
beginning null denotation identifier handling
current peek token when starting path pratt parse: '{'
current token (just about to return path to null denotation): '{'
finished null denotation identifier path parsing - next is branching
values of lookahead: 'identifier' ',' 'identifier' '}'
can be struct expr: 'true', not a block: 'true'
struct/enum expr field validated to not be null
struct/enum expr field pushed back
struct/enum expr fields comma skipped
struct/enum expr field validated to not be null
struct/enum expr field pushed back
lack of comma detected in struct/enum expr fields - break
struct/enum expr about to parse struct base
struct/enum expr skipped right curly - done and ready to return
beginning null denotation self/self-alias/dollar/crate/super handling
current peek token when starting path pratt parse: '.'
current token (just about to return path to null denotation): '.'
just finished parsing path (going to disambiguate) - peeked token is '.'
beginning null denotation self/self-alias/dollar/crate/super handling
current peek token when starting path pratt parse: '.'
current token (just about to return path to null denotation): '.'
just finished parsing path (going to disambiguate) - peeked token is '.'
beginning null denotation identifier handling
current peek token when starting path pratt parse: '.'
current token (just about to return path to null denotation): '.'
finished null denotation identifier path parsing - next is branching
beginning null denotation identifier handling
current peek token when starting path pratt parse: '.'
current token (just about to return path to null denotation): '.'
finished null denotation identifier path parsing - next is branching
successfully parsed inherent impl
beginning null denotation identifier handling
current peek token when starting path pratt parse: '::'
current token (just about to return path to null denotation): '('
finished null denotation identifier path parsing - next is branching
beginning null denotation identifier handling
current peek token when starting path pratt parse: '::'
current token (just about to return path to null denotation): '('
finished null denotation identifier path parsing - next is branching
beginning null denotation identifier handling
current peek token when starting path pratt parse: '::'
current token (just about to return path to null denotation): '('
finished null denotation identifier path parsing - next is branching
beginning null denotation identifier handling
current peek token when starting path pratt parse: ','
current token (just about to return path to null denotation): ','
finished null denotation identifier path parsing - next is branching
beginning null denotation identifier handling
current peek token when starting path pratt parse: ')'
current token (just about to return path to null denotation): ')'
finished null denotation identifier path parsing - next is branching
beginning null denotation identifier handling
current peek token when starting path pratt parse: '.'
current token (just about to return path to null denotation): '.'
finished null denotation identifier path parsing - next is branching
SUCCESSFULLY PARSED CRATE
ran register_plugins (with no body)
SUCCESSFULLY REGISTERED PLUGINS
started injection
finished injection
SUCCESSFULLY FINISHED INJECTION
started expansion
finished expansion
SUCCESSFULLY FINISHED EXPANSION
/home/mark/gccrs/gcc/testsuite/rust.test/compile/methods1.rs:38:9: warning: unused name 'sum'
38 | let sum = rect.sum_x();
| ^
Analyzing compilation unit
/home/mark/gccrs/gcc/testsuite/rust.test/compile/methods1.rs: In function ‘Rectangle_sum_x’:
/home/mark/gccrs/gcc/testsuite/rust.test/compile/methods1.rs:26:5: error: type mismatch in binary expression
26 | fn sum_x(self) -> f64 {
| ^
f64
<float:80>
<float:80>
D.227 = _2 + _4;
/home/mark/gccrs/gcc/testsuite/rust.test/compile/methods1.rs:26:5: internal compiler error: ‘verify_gimple’ failed
0x8b114e4 verify_gimple_in_seq(gimple*)
../../gccrs/gcc/tree-cfg.c:5157
0x881a9e3 gimplify_body(tree_node*, bool)
../../gccrs/gcc/gimplify.c:15401
0x881abb2 gimplify_function_tree(tree_node*)
../../gccrs/gcc/gimplify.c:15472
0x8675c88 cgraph_node::analyze()
../../gccrs/gcc/cgraphunit.c:670
0x8678a58 analyze_functions
../../gccrs/gcc/cgraphunit.c:1236
0x8679641 symbol_table::finalize_compilation_unit()
../../gccrs/gcc/cgraphunit.c:2514
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2021-06-01 22:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 22:31 ppc64le added to buildbot Mark Wielaard
2021-06-01 22:34 ` Mark Wielaard [this message]
2021-06-02 10:22 ` debian-i386 target (Was: ppc64le added to buildbot) Philip Herron
2021-06-02 10:25 ` John Paul Adrian Glaubitz
2021-06-02 21:14 ` Mark Wielaard
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=YLa12/31P0nqbbNA@wildebeest.org \
--to=mark@klomp.org \
--cc=gcc-rust@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).