public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59654] [OOP] Broken function table with complex OO use case
Date: Wed, 01 Jan 2014 13:40:00 -0000 [thread overview]
Message-ID: <bug-59654-4-CMqJ6aFCE0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59654-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-01-01
CC| |janus at gcc dot gnu.org
Summary|Broken function table with |[OOP] Broken function table
|complex OO use case |with complex OO use case
Ever confirmed|0 |1
Known to fail| |4.8.1, 4.9.0
--- Comment #7 from janus at gcc dot gnu.org ---
I can confirm the (supposedly wrong) runtime behavior with 4.8 and trunk. 4.7
does not compile the test case.
Uncommenting the private statement in line 144 only changes the behavior with
4.8, but my trunk build still yields the 'wrong' output.
I tried to use -fdump-tree-original to see what changes in the generated code
when flipping the private statement with 4.8, but that does not show *any*
difference.
next prev parent reply other threads:[~2014-01-01 13:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 1:25 [Bug fortran/59654] New: " Thomas.L.Clune at nasa dot gov
2014-01-01 1:27 ` [Bug fortran/59654] " Thomas.L.Clune at nasa dot gov
2014-01-01 4:02 ` kargl at gcc dot gnu.org
2014-01-01 4:27 ` Thomas.L.Clune at nasa dot gov
2014-01-01 4:53 ` Thomas.L.Clune at nasa dot gov
2014-01-01 13:40 ` janus at gcc dot gnu.org [this message]
2014-01-01 14:13 ` [Bug fortran/59654] [OOP] " Thomas.L.Clune at nasa dot gov
2014-01-01 23:25 ` janus at gcc dot gnu.org
2014-01-02 9:57 ` anlauf at gmx dot de
2014-01-02 11:08 ` janus at gcc dot gnu.org
2014-01-02 12:43 ` janus at gcc dot gnu.org
2014-01-02 13:51 ` janus at gcc dot gnu.org
2014-01-02 14:01 ` [Bug fortran/59654] [4.8/4.9 Regression] " janus at gcc dot gnu.org
2014-01-02 16:15 ` janus at gcc dot gnu.org
2014-01-02 17:27 ` janus at gcc dot gnu.org
2014-01-02 17:56 ` janus at gcc dot gnu.org
2014-01-02 20:51 ` Thomas.L.Clune at nasa dot gov
2014-01-02 21:59 ` janus at gcc dot gnu.org
2014-01-02 23:51 ` rouson at stanford dot edu
2014-01-03 9:15 ` burnus at gcc dot gnu.org
2014-01-04 13:27 ` Thomas.L.Clune at nasa dot gov
2014-01-04 16:47 ` janus at gcc dot gnu.org
2014-01-04 16:51 ` janus at gcc dot gnu.org
2014-01-04 18:54 ` dominiq at lps dot ens.fr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-59654-4-CMqJ6aFCE0@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).