Hi! On 2021-09-24T10:30:15+0200, I wrote: > I'm preparing a merge from GCC upstream into GCC/Rust.
Pushed to master branch commit 28f527c9598339cf834a30b5ee1f14258b8ecbb2 "Merge commit '2961ac45b9e19523958757e607d11c5893d6368b' [#247]". > 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. 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 -- Gcc-rust mailing list Gcc-rust@gcc.gnu.org https://gcc.gnu.org/mailman/listinfo/gcc-rust
