--- Comment #26 from ebotcazou at gcc dot gnu dot org 2005-11-06 08:42
---
How does stopping violate the standard? If the standard says behavior is
undefined, then you can do anything you want, including stopping.
You're confusing compile time and run time. Please read the whole
--- Comment #25 from appfault at hotmail dot com 2005-11-06 07:26 ---
How does stopping violate the standard? If the standard says behavior is
undefined, then you can do anything you want, including stopping.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10719
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-09-14
06:15 ---
I still say generating code that is not executable is a ridiculous way to
handle this ambiguity in the standard...
You still don't get the point. Read again comment #2, the bottom line is that
it's
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-14
06:25 ---
as promoted according to the default argument promotions is what makes this
undefined by the way.
char is promoted to int.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10719
--- Additional Comments From appfault at hotmail dot com 2005-09-14 16:09
---
Ok, so that's the best code it can generate, fine. So if instant segfault is
the best possible generated code, I think NOT generating any code is far more
helpful to the user. If not generating any code
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-09-14
16:23 ---
Ok, so that's the best code it can generate, fine. So if instant segfault is
the best possible generated code, I think NOT generating any code is far more
helpful to the user. If not generating any
--- Additional Comments From appfault at hotmail dot com 2005-09-15 04:22
---
Yes well I don't think you should have to go out of your way to ask the
compiler to not generate invalid code. Not generating invalid code should be
the default behavior.
We're talking about the difference
--- Additional Comments From ebotcazou at gcc dot gnu dot org 2005-09-15
04:52 ---
Yes well I don't think you should have to go out of your way to ask the
compiler to not generate invalid code. Not generating invalid code should be
the default behavior.
Again the compiler
--- Additional Comments From falk at debian dot org 2005-09-13 06:19
---
(In reply to comment #16)
Oh? I had -Werror on, and was not getting any warning at all from my code
that
was generating 'int $0x5' with gcc 3.4.1. It's perhaps a slightly different
case than comment 0,
--- Additional Comments From appfault at hotmail dot com 2005-09-14 00:16
---
Ok, disregard comment 16, the issue I saw was the same as comment 0.
Unfortunately, there was a '-w' sneakily in a 3rd-party makefile which hid the
warning. Maybe I should open another zilla for warning
--- Additional Comments From falk at debian dot org 2005-09-12 19:19
---
(In reply to comment #14)
Why not reopen this to add a -Wundefined-behavior, so that at least bugs like
that could be caught up front when using -Werror?
There is already an unconditional warning, so what
--- Additional Comments From appfault at hotmail dot com 2005-09-12 23:34
---
Oh? I had -Werror on, and was not getting any warning at all from my code that
was generating 'int $0x5' with gcc 3.4.1. It's perhaps a slightly different
case than comment 0, because I was casting an int
--- Additional Comments From appfault at hotmail dot com 2005-09-11 08:04
---
Invalid? So whenever behavior is undefined by the C standard, would it be ok
to delete the user's harddrive as well? This is ridiculous - fix the bug.
--
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-11
14:34 ---
(In reply to comment #12)
Invalid? So whenever behavior is undefined by the C standard, would it be ok
to delete the user's harddrive as well? This is ridiculous - fix the bug.
It is undefined which
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-05
07:29 ---
Reopening to ...
--
What|Removed |Added
Status|RESOLVED
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-05
07:29 ---
Mark as invalid.
--
What|Removed |Added
Status|REOPENED
16 matches
Mail list logo
