public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc <dkm@kataplop.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Marc <dkm@kataplop.net>,  gcc-rust@gcc.gnu.org
Subject: Re: Test results for gccrs on Debian unstable ia64
Date: Wed, 02 Jun 2021 19:02:44 +0200	[thread overview]
Message-ID: <87mts8yzbf.fsf@arrakis.kataplop.net> (raw)
In-Reply-To: <0306dfc3-f2ac-fbef-6cfe-8d1bed93d5cd@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Wed, 2 Jun 2021 19:00:07 +0200")

John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:

> Hi Marc!
>
> On 6/2/21 6:58 PM, Marc wrote:
>> Thanks for testing this! IIUC, this is an issue on our side, so I'll
>> open an issue.
>
> Let me test a plain GCC build with just C and C++ first to make sure it's
> not a general GCC problem on ia64.
>
> libunwind on ia64 can be a bit tricky sometimes, so it might not be gccrs
> which is to be blamed here.

Ah, sorry, already opened :). I'll close it if needed !

https://github.com/Rust-GCC/gccrs/issues/474

Marc

  reply	other threads:[~2021-06-02 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 11:27 John Paul Adrian Glaubitz
2021-06-02 12:41 ` Marc
2021-06-02 12:47   ` John Paul Adrian Glaubitz
2021-06-02 13:05     ` Marc
2021-06-02 13:08       ` John Paul Adrian Glaubitz
2021-06-02 16:14         ` John Paul Adrian Glaubitz
2021-06-02 16:58           ` Marc
2021-06-02 17:00             ` John Paul Adrian Glaubitz
2021-06-02 17:02               ` Marc [this message]
2021-06-02 20:39                 ` John Paul Adrian Glaubitz

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=87mts8yzbf.fsf@arrakis.kataplop.net \
    --to=dkm@kataplop.net \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=glaubitz@physik.fu-berlin.de \
    /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).