This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/61597] Unexpected behavior at runtime
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 25 Jun 2014 16:56:04 +0000
- Subject: [Bug c++/61597] Unexpected behavior at runtime
- Auto-submitted: auto-generated
- References: <bug-61597-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61597
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Last reconfirmed|2014-06-24 00:00:00 |2014-06-25
CC| |manu at gcc dot gnu.org
Resolution|INVALID |---
Ever confirmed|0 |1
--- Comment #18 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #17)
> And if func is inline,
> it will require -fkeep-inline-functions.
What is the difference between inline/not inline?
> e.cc: In function 'Iter& func(Iter, int)':
> e.cc:11:20: warning: function returns address of local variable
> [-Wreturn-local-addr]
> return iter += n;
> ^
Why it points to n?