public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/31279] Uninitialized warning for call-by-reference arguments with known intent(in)
2007-03-20 15:42 [Bug middle-end/31279] New: Uninitialized warning for call-by-reference arguments with known intent(in) burnus at gcc dot gnu dot org
@ 2007-03-20 15:42 ` burnus at gcc dot gnu dot org
0 siblings, 0 replies; 6+ messages in thread
From: burnus at gcc dot gnu dot org @ 2007-03-20 15:42 UTC (permalink / raw)
To: gcc-bugs
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31279
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug middle-end/31279] New: Uninitialized warning for call-by-reference arguments with known intent(in)
@ 2007-03-20 15:42 burnus at gcc dot gnu dot org
2007-03-20 15:42 ` [Bug middle-end/31279] " burnus at gcc dot gnu dot org
0 siblings, 1 reply; 6+ messages in thread
From: burnus at gcc dot gnu dot org @ 2007-03-20 15:42 UTC (permalink / raw)
To: gcc-bugs
In Fortran one can specify the intent of variables thus if all arguments have
INTENT(IN) then GCC should be able to detect that alist in the call to cshift
is uninitialized.
This depends on the middle end support of intents (PR31094) plus using these in
gfortran.
Example (using an intrinsic function):
program testcshft
integer :: alist(4)
alist =cshift(alist,-1)
write(*,*) alist
end program testcshft
--
Summary: Uninitialized warning for call-by-reference arguments
with known intent(in)
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
BugsThisDependsOn: 31094
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31279
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug middle-end/31279] Uninitialized warning for call-by-reference arguments with known intent(in)
[not found] <bug-31279-4@http.gcc.gnu.org/bugzilla/>
` (2 preceding siblings ...)
2013-08-28 8:25 ` rguenth at gcc dot gnu.org
@ 2020-05-19 20:03 ` msebor at gcc dot gnu.org
3 siblings, 0 replies; 6+ messages in thread
From: msebor at gcc dot gnu.org @ 2020-05-19 20:03 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31279
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=10138
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
In conjunction with attribute access (read_only) (which I presume is the moral
equivalent of INTENT(IN)), the patch I submitted for pr10138 puts in place the
infrastructure to implement this warning for FORTRAN as well. All that it
should need is mapping INTENT(IN) to the attribute.
https://gcc.gnu.org/pipermail/gcc-patches/2020-May/545856.html
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug middle-end/31279] Uninitialized warning for call-by-reference arguments with known intent(in)
[not found] <bug-31279-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 17:49 ` pinskia at gcc dot gnu.org
2013-06-25 9:10 ` dominiq at lps dot ens.fr
@ 2013-08-28 8:25 ` rguenth at gcc dot gnu.org
2020-05-19 20:03 ` msebor at gcc dot gnu.org
3 siblings, 0 replies; 6+ messages in thread
From: rguenth at gcc dot gnu.org @ 2013-08-28 8:25 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31279
Bug 31279 depends on bug 31094, which changed state.
Bug 31094 Summary: Support annotating function parameters as read-only and/or non-escaping
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31094
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug middle-end/31279] Uninitialized warning for call-by-reference arguments with known intent(in)
[not found] <bug-31279-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 17:49 ` pinskia at gcc dot gnu.org
@ 2013-06-25 9:10 ` dominiq at lps dot ens.fr
2013-08-28 8:25 ` rguenth at gcc dot gnu.org
2020-05-19 20:03 ` msebor at gcc dot gnu.org
3 siblings, 0 replies; 6+ messages in thread
From: dominiq at lps dot ens.fr @ 2013-06-25 9:10 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31279
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Still no warning at revision 200371.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug middle-end/31279] Uninitialized warning for call-by-reference arguments with known intent(in)
[not found] <bug-31279-4@http.gcc.gnu.org/bugzilla/>
@ 2012-02-02 17:49 ` pinskia at gcc dot gnu.org
2013-06-25 9:10 ` dominiq at lps dot ens.fr
` (2 subsequent siblings)
3 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2012-02-02 17:49 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31279
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-02-02
Ever Confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-02 17:49:32 UTC ---
Confirmed.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2020-05-19 20:03 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-03-20 15:42 [Bug middle-end/31279] New: Uninitialized warning for call-by-reference arguments with known intent(in) burnus at gcc dot gnu dot org
2007-03-20 15:42 ` [Bug middle-end/31279] " burnus at gcc dot gnu dot org
[not found] <bug-31279-4@http.gcc.gnu.org/bugzilla/>
2012-02-02 17:49 ` pinskia at gcc dot gnu.org
2013-06-25 9:10 ` dominiq at lps dot ens.fr
2013-08-28 8:25 ` rguenth at gcc dot gnu.org
2020-05-19 20:03 ` msebor at gcc dot gnu.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).