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
Hi Thomas!
On 9/24/21 10:30, Thomas Schwinge wrote:
> 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?
I'm fine with testing after the merge and I'll report issues as they show
up.
Thanks for asking!
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
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --] Thanks for reaching out to continue helping with this Adrian, what is it like building on some of your systems, does it take a long time? It would be nice to track this in some kind of built matrix, would you be interested in carving out a wiki page over on https://github.com/Rust-GCC/gccrs/wiki? Or do you have any other ideas? Thanks --Phil On Fri, 24 Sept 2021 at 10:25, John Paul Adrian Glaubitz < glaubitz@physik.fu-berlin.de> wrote: > Hi Thomas! > > On 9/24/21 10:30, Thomas Schwinge wrote: > > 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? > > I'm fine with testing after the merge and I'll report issues as they show > up. > > Thanks for asking! > > 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 > > -- > Gcc-rust mailing list > Gcc-rust@gcc.gnu.org > https://gcc.gnu.org/mailman/listinfo/gcc-rust > [-- Attachment #2: Type: text/html, Size: 1972 bytes --]
Hi Philipp!
On 9/24/21 13:20, Philip Herron wrote:
> Thanks for reaching out to continue helping with this Adrian, what is it
> like building on some of your systems, does it take a long time?
>
> It would be nice to track this in some kind of built matrix, would you be
> interested in carving out a wiki page over on
> https://github.com/Rust-GCC/gccrs/wiki? Or do you have any other ideas?
Sure, if you want a matrix with build times, I can create one.
I'm currently on vacation and could work on that next week.
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
Hi Thomas, On Fri, Sep 24, 2021 at 10:30:15AM +0200, Thomas Schwinge wrote: > 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>: Thanks for doing this. > 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? I don't run the builds by hand, the buildbot workers (debian-arm64, debian-i386, fedora-ppc64, fedora-ppc64le, fedora-s390x, fedora-x86_64) simply build every new commit they see: https://builder.wildebeest.org/buildbot/#/builders?tags=gccrust They are currently all green. If any turns red, they should sent an email to the list and I'll take a look and try to fix them up. Cheers, Mark
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