public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rouson at stanford dot edu" <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: Thu, 02 Jan 2014 23:51:00 -0000 [thread overview] Message-ID: <bug-59654-4-HmhBARDsSE@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 #20 from Damian Rouson <rouson at stanford dot edu> --- FYI, the current port of gcc49 via macports is broken (https://trac.macports.org/ticket/41964) so I think Tom’s only choice will be to build from source or build on another platform unless the port gets fixed. Damian On Jan 2, 2014, at 1:59 PM, janus at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654 > > --- Comment #19 from janus at gcc dot gnu.org --- > (In reply to tlcclt from comment #18) >> I usually just use mac port these days > > Apparently MacPorts does have GCC trunk snapshots. Tbe current one is from > 2013-12-29 and I think they are updated weekly, so you might have to wait a few > days. > > >> With regard to the back port in 4.8, would that appear only in 4.8.3? Or >> would it possibly also go into 4.8.2/4.8.1. > > No, 4.8.1 and 4.8.2 have been released already. The fix would go into the > upcoming 4.8.3. > > >> Thank you so much for such a speedy resolution. > > Thanks for the bug report! > > -- > You are receiving this mail because: > You are on the CC list for the bug. >From gcc-bugs-return-438952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 00:03:00 2014 Return-Path: <gcc-bugs-return-438952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 1079 invoked by alias); 3 Jan 2014 00:02:59 -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 1060 invoked by uid 48); 3 Jan 2014 00:02:55 -0000 From: "bruck.michael at googlemail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59661] New: documentation: __builtin_FUNCTION / _FILE listed as returning int Date: Fri, 03 Jan 2014 00:02:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: minor X-Bugzilla-Who: bruck.michael at googlemail 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter Message-ID: <bug-59661-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/msg00094.txt.bz2 Content-length: 688 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59661 Bug ID: 59661 Summary: documentation: __builtin_FUNCTION / _FILE listed as returning int Product: gcc Version: unknown Status: UNCONFIRMED Severity: minor Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: bruck.michael at googlemail dot com http://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html lists: — Built-in Function: int __builtin_FUNCTION () ... — Built-in Function: int __builtin_FILE () ... These should return some sort of string (ideally constexpr?). >From gcc-bugs-return-438953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 00:42:29 2014 Return-Path: <gcc-bugs-return-438953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 17273 invoked by alias); 3 Jan 2014 00:42:28 -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 17232 invoked by uid 48); 3 Jan 2014 00:42:25 -0000 From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/59661] documentation: __builtin_FUNCTION / _FILE listed as returning int Date: Fri, 03 Jan 2014 00:42: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: 4.9.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW 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: keywords bug_status cf_reconfirmed_on cc version everconfirmed bug_severity Message-ID: <bug-59661-4-Svstsj5NGU@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-59661-4@http.gcc.gnu.org/bugzilla/> References: <bug-59661-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/msg00095.txt.bz2 Content-length: 730 http://gcc.gnu.org/bugzilla/show_bug.cgi?idY661 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |documentation Status|UNCONFIRMED |NEW Last reconfirmed| |2014-01-03 CC| |rguenth at gcc dot gnu.org Version|unknown |4.9.0 Ever confirmed|0 |1 Severity|minor |normal --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed.
next prev parent reply other threads:[~2014-01-02 23:51 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 [this message] 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-HmhBARDsSE@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).