public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Philip Herron <philip.herron@embecosm.com>,
	Mark Wielaard <mark@klomp.org>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: debian-i386 target (Was: ppc64le added to buildbot)
Date: Wed, 2 Jun 2021 12:25:35 +0200	[thread overview]
Message-ID: <93db9426-faa5-b037-d07b-d80b805f4004@physik.fu-berlin.de> (raw)
In-Reply-To: <CAB2u+n3pJFuryTDEU5-RHf1AyNVoAsDZhX1b-zmhm7jD+rsf6w@mail.gmail.com>

Hi Philip!

On 6/2/21 12:22 PM, Philip Herron wrote:
> This is a good find I will open an issue to track this, I have a local
> Debian 32 bit machine at home so I can try this on later in the week. Off
> the top of my head I am wondering if there is something wrong with how we
> are building up the integer tree nodes. The relevant code starts in
> gcc/rust/backend/rust-compile-tyty.h inside ```  void visit (TyTy::IntType
> &type) override```.

I have access to quite a number of different architectures and I will start
testing gccrs on all of them now, starting with ia64 :-).

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2021-06-02 10:25 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 ` debian-i386 target (Was: ppc64le added to buildbot) Mark Wielaard
2021-06-02 10:22   ` Philip Herron
2021-06-02 10:25     ` John Paul Adrian Glaubitz [this message]
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=93db9426-faa5-b037-d07b-d80b805f4004@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=mark@klomp.org \
    --cc=philip.herron@embecosm.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).