GCC undefined behaviors are getting wild

Re:GCC undefined behaviors are getting wild by tmtvl on Monday November 28, 2022 @07:18AM (#33772692)

It is undefined behaviour if I write GCC --hlep

Well no, it's a compilation error, you need at the very least a semicolon after hlep and from there on it depends on what GCC is. If it's a function you need parentheses around --hlep, if it's a type you need to remove the --, if it's a variable you need to put a semicolon after it,...

Because GCC is all-caps I'm guessing it's a macro, so here's an example of how you could write it (though it won't be UB): https://godbolt.org/z/dYMddrTjj

[ Parent | on HN ]

Re:GCC undefined behaviors are getting wild by benj111 on Monday November 28, 2022 @07:58AM (#33773041)

I'm not sure if you're supporting my pov by showing the absurdity of the other position???

Yeah sure, if my phone auto incorrects gcc to GCC then that is technically meaningless so you're completely free to interpret my comment how you want.

..... Although..... GCC stands for GNU Compiler Collection so it can be reasonably capitalised, so maybe then, rather than saying anything goes we should do something reasonable because then you aren't left saying something really stupid if you're wrong???

[ Parent | on HN ]

Re:GCC undefined behaviors are getting wild by gpderetta on Monday November 28, 2022 @11:41AM (#33775813)

Parent point is when the standard talks about UB it refers about translating C code. So parent cheekly interpreted your comment about command line flags (which are outside the remit of the standard) as code instead. I thought it was fitting.

[ Parent | on HN ]