public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Arthur Cohen <arthur.cohen@embecosm.com>
Cc: Thomas Schwinge <thomas@codesourcery.com>,
	gcc-patches@gcc.gnu.org, Richard Biener <rguenther@suse.de>,
	Gaius Mulley <gaiusmod2@gmail.com>,
	gcc-rust@gcc.gnu.org
Subject: Re: Rust: In 'type_for_mode' langhook also consider all 'int_n' modes/types (was: Modula-2 / Rust: Many targets failing)
Date: Fri, 24 Feb 2023 10:12:07 +0100	[thread overview]
Message-ID: <20230224091207.wkjywpn4vtnbbsbi@lug-owl.de> (raw)
In-Reply-To: <72370753-46f9-ec0e-9098-9ecdf3328484@embecosm.com>

[-- Attachment #1: Type: text/plain, Size: 1720 bytes --]

Hi Thomas / Arthur!

On Wed, 2023-02-22 15:30:37 +0100, Arthur Cohen <arthur.cohen@embecosm.com> wrote:
[..]
> > >   --target=msp430-elfbare
> > > ~~~~~~~~~~~~~~~~~~~~~~~~~
> > >        /var/lib/laminar/run/gcc-msp430-elfbare/24/toolchain-build/./gcc/xgcc -B/var/lib/laminar/run/gcc-msp430-elfbare/24/toolchain-build/./gcc/  -xrust -frust-incomplete-and-experimental-compiler-do-not-use -nostdinc /dev/null -S -o /dev/null -fself-test=../../gcc/gcc/testsuite/selftests
> > >        <built-in>: internal compiler error: Segmentation fault
> > >        0xf2efbf crash_signal
> > >              ../../gcc/gcc/toplev.cc:314
> > >        0x120c8c7 build_function_type(tree_node*, tree_node*, bool)
> > >              ../../gcc/gcc/tree.cc:7360
> > >        0x120cc20 build_function_type_list(tree_node*, ...)
> > >              ../../gcc/gcc/tree.cc:7442
> > >        0x120d16b build_common_builtin_nodes()
> > >              ../../gcc/gcc/tree.cc:9883
> > >        0x8449b4 grs_langhook_init
> > >              ../../gcc/gcc/rust/rust-lang.cc:132
> > >        0x8427b2 lang_dependent_init
> > >              ../../gcc/gcc/toplev.cc:1815
> > >        0x8427b2 do_compile
> > >              ../../gcc/gcc/toplev.cc:2110
> > >        Please submit a full bug report, with preprocessed source (by using -freport-bug).
> > >        Please include the complete backtrace with any bug report.
> > >        See <https://gcc.gnu.org/bugs/> for instructions.
> > >        make[1]: *** [../../gcc/gcc/rust/Make-lang.in:275: s-selftest-rust] Error 1

Confirmed successful build #37 for my msp320-elfbare build at
http://toolchain.lug-owl.de/laminar/jobs/gcc-msp430-elfbare

Thanks,
  Jan-Benedict

-- 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2023-02-24  9:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221219212344.ewtuzd2jtztm77x2@lug-owl.de>
2023-02-22 11:25 ` Thomas Schwinge
2023-02-22 11:45   ` Richard Biener
2023-02-22 14:30   ` Arthur Cohen
2023-02-24  9:12     ` Jan-Benedict Glaw [this message]
2023-02-25 22:20   ` Jan-Benedict Glaw

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=20230224091207.wkjywpn4vtnbbsbi@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=arthur.cohen@embecosm.com \
    --cc=gaiusmod2@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=rguenther@suse.de \
    --cc=thomas@codesourcery.com \
    /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).