public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Thomas.L.Clune at nasa dot gov" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/59654] [4.8/4.9 Regression] [OOP] Broken function table with complex OO use case Date: Sat, 04 Jan 2014 13:27:00 -0000 [thread overview] Message-ID: <bug-59654-4-4WwtgBpVFZ@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 --- Comment #22 from tlcclt <Thomas.L.Clune at nasa dot gov> --- Success! I had to manually edit the configure file for the latest gcc to build on my Mac. (a few -Werror=…) were blocking the compilation. Looks like that should be off by default, but somehow is not. Anyway, I was able to build the gcc. And … it _fixed_ the problem in the real code! Thanks so much for all the assistance. >From gcc-bugs-return-439039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 14:21:34 2014 Return-Path: <gcc-bugs-return-439039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 2719 invoked by alias); 4 Jan 2014 14:21:34 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 2666 invoked by uid 48); 4 Jan 2014 14:21:29 -0000 From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/59654] [4.8/4.9 Regression] [OOP] Broken function table with complex OO use case Date: Sat, 04 Jan 2014 14:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: janus at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: janus at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59654-4-4EPwKrEwqB@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59654-4@http.gcc.gnu.org/bugzilla/> References: <bug-59654-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-01/txt/msg00181.txt.bz2 Content-length: 298 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654 --- Comment #23 from janus at gcc dot gnu.org --- (In reply to tlcclt from comment #22) > Anyway, I was able to build the gcc. And … it _fixed_ the problem in the > real code! Great, thanks for checking. Will apply the backport soon. >From gcc-bugs-return-439040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 16:16:15 2014 Return-Path: <gcc-bugs-return-439040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 11040 invoked by alias); 4 Jan 2014 16:16:14 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 11009 invoked by uid 55); 4 Jan 2014 16:16:10 -0000 From: "christos at zoulas dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59674] On m68k and vax variables stack variables with > MAX_STACK_ALIGNMENT make ssp fail Date: Sat, 04 Jan 2014 16:16:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: christos at zoulas dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-59674-4-rQZ2zWMljV@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59674-4@http.gcc.gnu.org/bugzilla/> References: <bug-59674-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-01/txt/msg00182.txt.bz2 Content-length: 648 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY674 --- Comment #2 from Christos Zoulas <christos at zoulas dot com> --- On Jan 4, 11:20am, gcc-bugzilla@gcc.gnu.org ("mikpelinux at gmail dot com") wrote: -- Subject: [Bug c/59674] On m68k and vax variables stack variables with > MA | http://gcc.gnu.org/bugzilla/show_bug.cgi?idY674 | | --- Comment #1 from Mikael Pettersson <mikpelinux at gmail dot com> --- | Works, as in generates OK looking code w/o issuing any diagnostics, on both | m68k-linux and vax-linux for me. A NetBSD issue? Are you using a native compiler or a cross-compiler? We are using a cross compiler from amd64. christos
next prev parent reply other threads:[~2014-01-04 13:27 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 ` [Bug fortran/59654] [OOP] " janus at gcc dot gnu.org 2014-01-01 14:13 ` 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 [this message] 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-4WwtgBpVFZ@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: linkBe 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).