Re: Merge from GCC upstream into GCC/Rust

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 ou

Re: Merge from GCC upstream into GCC/Rust

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?

Re: byte/char string representation (Was: [PATCH] Fix byte char and byte string lexing code)

Hi Mark, This is really useful information, will this mean that the lexer token will need to represent strings differently as well? Or is the std::string in the lexer still ok? The change you made above has the problem that reference types like, arrays are forms of what rust calls covariant types

Re: Merge from GCC upstream into GCC/Rust

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

Merge from GCC upstream into GCC/Rust

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 : | Aside from the GCC/Rust-specific files (not existing in GCC upstream),