Rust Compatibility

[Philip Herron <philip.herron@embecosm.com>]

[-- Attachment #1: Type: text/plain, Size: 1387 bytes --]

Hi everyone,

Yesterday this issue was posted to us on GitHub
https://github.com/Rust-GCC/gccrs/issues/653, which revolves around
strict-aliasing rules.

The conversation was focused on what level of compatibility we are aiming
for in the Rust language. This is important, and I don't believe we should
allow specific language features/development outside the official Rust
processes. This means we do not want to have any GCC specific attributes or
language features and we won't provide a shortcut to bypass RFC processes.

Though I believe we should always allow users to invoke GCC Rust however
they wish (since the FE inherits the common GCC options), this is the point
of free software to me. To mitigate any GCC vs Rustc incompatibility, our
cargo-gccrs wrapper was always intended to map rust arguments over to the
GCC version of these to get the intended Rustc behaviour. But still, when
users want to invoke gccrs directly, it is up to them to choose what
options they want, good or bad, including using gcc-plugins.

Some of the feedback seems that if we allow users to compile code with or
without strict aliasing, this may allow for code to compile with GCC but
not with rustc which "splits the ecosystem". So I wanted to run this by you
guys here to get feedback on what people think about allowing users to
choose their GCC compilation options in general.

Thanks

--Phil

[-- Attachment #2: Type: text/html, Size: 1524 bytes --]