Displaying 2 results from an estimated 2 matches for "compilerb".
Did you mean:
compiler
2015 Jul 01
2
[LLVMdev] C as used/implemented in practice: analysis of responses
...ndefined behaviour in each standard. Worse
still, you have divided the programmers in two classes: those that
play it safe, and those that don't, essentially creating two different
programming languages. Code that compiles and work with
compilerA+safe_mode will not necessarily compile/work with
compilerB+safe_mode or compilerA+full_mode either.
C and C++ are already complicated enough, with so many standard levels
to implement (C90, C99, C11, C++03, C++11, C++14, etc) that
duplicating each and everyone of them, *per compiler*, is not
something you want to do.
That will, ultimately, move compilers...
2015 Jul 01
2
[LLVMdev] C as used/implemented in practice: analysis of responses
On 1 July 2015 at 15:20, Russell Wallace <russell.wallace at gmail.com> wrote:
> Group all monkey's paw optimisations together, and enable them only if an
> extra compiler flag is supplied. Or failing that, at least have a compiler
> flag that will disable all of them (while leaving all the safe optimisations
> enabled).
So, are you suggesting we get rid of all undefined AND