public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
[not found] <bug-44604-4@http.gcc.gnu.org/bugzilla/>
@ 2013-06-11 20:24 ` dominiq at lps dot ens.fr
2013-06-17 15:05 ` dominiq at lps dot ens.fr
2014-12-06 0:09 ` dominiq at lps dot ens.fr
2 siblings, 0 replies; 7+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-06-11 20:24 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2013-06-11
Ever confirmed|0 |1
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Works for me on 4.6.4, 4.7.3, 4.8.1, and trunk. Confirmed for 4.5.4. Apparently
fixed between revisions 179850 and 179999. This PR could probably be closed as
fixed.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
[not found] <bug-44604-4@http.gcc.gnu.org/bugzilla/>
2013-06-11 20:24 ` [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals dominiq at lps dot ens.fr
@ 2013-06-17 15:05 ` dominiq at lps dot ens.fr
2014-12-06 0:09 ` dominiq at lps dot ens.fr
2 siblings, 0 replies; 7+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-06-17 15:05 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Waiting.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
[not found] <bug-44604-4@http.gcc.gnu.org/bugzilla/>
2013-06-11 20:24 ` [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals dominiq at lps dot ens.fr
2013-06-17 15:05 ` dominiq at lps dot ens.fr
@ 2014-12-06 0:09 ` dominiq at lps dot ens.fr
2 siblings, 0 replies; 7+ messages in thread
From: dominiq at lps dot ens.fr @ 2014-12-06 0:09 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Works for me also for 4.9.2 and trunk (5.0 r218434). No answer for almost a
year and a half. Closing as FIXED.
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
2010-06-21 7:02 [Bug fortran/44604] New: " burnus at gcc dot gnu dot org
` (2 preceding siblings ...)
2010-06-21 8:55 ` dominiq at lps dot ens dot fr
@ 2010-06-21 9:13 ` burnus at gcc dot gnu dot org
3 siblings, 0 replies; 7+ messages in thread
From: burnus at gcc dot gnu dot org @ 2010-06-21 9:13 UTC (permalink / raw)
To: gcc-bugs
------- Comment #4 from burnus at gcc dot gnu dot org 2010-06-21 09:13 -------
(In reply to comment #3)
> Is it not a duplicate of pr35203?
No. In this bug (PR 44604) one is in the caller and there one can distinguish
between address and value of a variable and the fix is relatively simple
(though requires some thinking and re-shoveling).
By contrast, PR 35203 requires a special handling of OPTIONAL + VALUE dummies,
where both the caller and the callee need to be involved by passing additional
information and making use of them.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
2010-06-21 7:02 [Bug fortran/44604] New: " burnus at gcc dot gnu dot org
2010-06-21 7:13 ` [Bug fortran/44604] " burnus at gcc dot gnu dot org
2010-06-21 7:24 ` burnus at gcc dot gnu dot org
@ 2010-06-21 8:55 ` dominiq at lps dot ens dot fr
2010-06-21 9:13 ` burnus at gcc dot gnu dot org
3 siblings, 0 replies; 7+ messages in thread
From: dominiq at lps dot ens dot fr @ 2010-06-21 8:55 UTC (permalink / raw)
To: gcc-bugs
------- Comment #3 from dominiq at lps dot ens dot fr 2010-06-21 08:55 -------
Is it not a duplicate of pr35203?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
2010-06-21 7:02 [Bug fortran/44604] New: " burnus at gcc dot gnu dot org
2010-06-21 7:13 ` [Bug fortran/44604] " burnus at gcc dot gnu dot org
@ 2010-06-21 7:24 ` burnus at gcc dot gnu dot org
2010-06-21 8:55 ` dominiq at lps dot ens dot fr
2010-06-21 9:13 ` burnus at gcc dot gnu dot org
3 siblings, 0 replies; 7+ messages in thread
From: burnus at gcc dot gnu dot org @ 2010-06-21 7:24 UTC (permalink / raw)
To: gcc-bugs
------- Comment #2 from burnus at gcc dot gnu dot org 2010-06-21 07:24 -------
Reminder: Same problem occurs when calling with %VAL(actual_arg).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals
2010-06-21 7:02 [Bug fortran/44604] New: " burnus at gcc dot gnu dot org
@ 2010-06-21 7:13 ` burnus at gcc dot gnu dot org
2010-06-21 7:24 ` burnus at gcc dot gnu dot org
` (2 subsequent siblings)
3 siblings, 0 replies; 7+ messages in thread
From: burnus at gcc dot gnu dot org @ 2010-06-21 7:13 UTC (permalink / raw)
To: gcc-bugs
------- Comment #1 from burnus at gcc dot gnu dot org 2010-06-21 07:13 -------
Seemingly the allocated/associated check
cond = fold_build2 (EQ_EXPR, boolean_type_node, parmse.expr,
fold_convert (TREE_TYPE (parmse.expr),
null_pointer_node));
in trans-expr.c's gfc_conv_procedure_call accesses the value of the variable
and not its location as parmse.expr is already dereferenced via gfc_conv_expr,
called by
else if (fsym && fsym->attr.value)
{
// [...]
gfc_conv_expr (&parmse, e);
}
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44604
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2014-12-06 0:09 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-44604-4@http.gcc.gnu.org/bugzilla/>
2013-06-11 20:24 ` [Bug fortran/44604] Wrong run-time checks with VALUE dummies and pointer/allocatable actuals dominiq at lps dot ens.fr
2013-06-17 15:05 ` dominiq at lps dot ens.fr
2014-12-06 0:09 ` dominiq at lps dot ens.fr
2010-06-21 7:02 [Bug fortran/44604] New: " burnus at gcc dot gnu dot org
2010-06-21 7:13 ` [Bug fortran/44604] " burnus at gcc dot gnu dot org
2010-06-21 7:24 ` burnus at gcc dot gnu dot org
2010-06-21 8:55 ` dominiq at lps dot ens dot fr
2010-06-21 9:13 ` burnus at gcc dot gnu dot org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).