From: Thomas Schwinge <thomas@codesourcery.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Mark Wielaard <mark@klomp.org>
Cc: <gcc-rust@gcc.gnu.org>
Subject: Merge from GCC upstream into GCC/Rust
Date: Fri, 24 Sep 2021 10:30:15 +0200 [thread overview]
Message-ID: <87czoyz888.fsf@euler.schwinge.homeip.net> (raw)
Hi "Testers"!
I'm preparing a merge from GCC upstream into GCC/Rust. This is normally
pretty unexciting ;-) -- the exception being, as once mentioned in
<https://github.com/Rust-GCC/gccrs/issues/247#issuecomment-812720604>:
| Aside from the GCC/Rust-specific files (not existing in GCC upstream),
| we also carry a lot of changes in 'gcc/config/' (GCC back ends
| implementations), originating in <https://github.com/SimplyTheOther>
| "@SimplyTheOther"'s work on Rust Target Hooks. For a few of these
| files/changes we run into merge conflicts (which I did sort out), but
| also this work may need updates corresponding to GCC upstream changes.
| As that work is (per the Git commit logs etc.) still very much work in
| progress, and I assume hasn't been tested with all the respective many
| GCC back ends, I'm not going to spend much effort on that, and just
| make sure that x86_64-pc-linux-gnu continues to work.
As for checking that the configurations that you're testing are still
fine, would you like to do (and/or fix) that before or after me pushing
the merge?
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next reply other threads:[~2021-09-24 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 8:30 Thomas Schwinge [this message]
2021-09-24 9:25 ` John Paul Adrian Glaubitz
2021-09-24 11:20 ` Philip Herron
2021-09-24 11:45 ` John Paul Adrian Glaubitz
2021-09-25 11:31 ` Mark Wielaard
2021-09-25 11:52 ` Thomas Schwinge
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=87czoyz888.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=mark@klomp.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).