https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.5 |---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.4 |8.5
--- Comment #13 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.3 |8.4
--- Comment #12 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.2 |8.3
--- Comment #11 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|8.0 |8.2
--- Comment #10 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
--- Comment #9 from janus at gcc dot gnu.org ---
(In reply to janus from comment #7)
> One thing that could be done instead is to mention the INTENTs of the
> arguments in the documentation:
>
> https://gcc.gnu.org/onlinedocs/gfortran/EXECUTE_005
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
Thomas Koenig changed:
What|Removed |Added
Keywords|wrong-code |documentation
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
--- Comment #7 from janus at gcc dot gnu.org ---
One thing that could be done instead is to mention the INTENTs of the arguments
in the documentation:
https://gcc.gnu.org/onlinedocs/gfortran/EXECUTE_005fCOMMAND_005fLINE.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to janus from comment #0)
> ==16313== Conditional jump or move depends on uninitialised value(s)
> ==16313==at 0x4F3B7EA: _gfortran_execute_command_line_i4 (in
> /usr/lib/x86_64-linux-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
--- Comment #5 from janus at gcc dot gnu.org ---
(In reply to janus from comment #2)
> Since it seems that execute_command_line always sets a return value for the
> exitstat argument, one probably does not need to check against an initial
> value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
--- Comment #3 from janus at gcc dot gnu.org ---
I have verified that the patch in comment 2 fixes the problem on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
Target Milestone|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
--- Comment #2 from janus at gcc dot gnu.org ---
Since it seems that execute_command_line always sets a return value for the
exitstat argument, one probably does not need to check against an initial value
at all:
Index: libgfortran/intrinsics/e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82962
--- Comment #1 from janus at gcc dot gnu.org ---
Possible patch:
Index: libgfortran/intrinsics/execute_command_line.c
===
--- libgfortran/intrinsics/execute_command_line.c (rev
15 matches
Mail list logo