public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "LpSolit at netscape dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/64968] Upgrade GCC Bugzilla to 5.0
Date: Wed, 11 Feb 2015 20:46:00 -0000	[thread overview]
Message-ID: <bug-64968-4-NsrBoHVAAP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64968-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64968

--- Comment #6 from Frédéric Buclin <LpSolit at netscape dot net> ---
Created attachment 34735
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34735&action=edit
GCC patch for 5.0, v1

No code changes compared to 4.4, but the patch for 4.4 didn't apply cleanly to
5.0 due to some context changes. So I rediffed it again, now using git.
>From gcc-bugs-return-476924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Feb 11 20:46:17 2015
Return-Path: <gcc-bugs-return-476924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30502 invoked by alias); 11 Feb 2015 20:46:16 -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 30385 invoked by uid 48); 11 Feb 2015 20:46:12 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/64927] [4.8 Regression] Surprising error with -Wsurprising (-Wall) and TRANSFER + C_ASSOCIATED
Date: Wed, 11 Feb 2015 20:46: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.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.8.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64927-4-rGjqqeZf4J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64927-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64927-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: 2015-02/txt/msg01257.txt.bz2
Content-length: 894

https://gcc.gnu.org/bugzilla/show_bug.cgi?idd927

--- Comment #8 from Harald Anlauf <anlauf at gmx dot de> ---
(In reply to Dominique d'Humieres from comment #6)
> > The revision numbers you refer to belong to the 4.9-branch.
>
> Indeed -> I was trying to find the commit that fixed the problem (without
> success).
>
> > IMO it is not fixed on 4.8. If there is no easy solution, I'd rather
> > prefer to mark it in an appropriate way (wontfix?), so that others
> > can see that this problem is known for particular gcc versions.
>
> I think the only "appropriate way" is FIXED as it is the case for 4.9 and
> trunk. Closing as WONTFIX will be misleading for these revisions. Note that
> 4.8 will be closed pretty soon.

My reasoning is based on the observation that Tobias Burnus
just closed PR64474 as WONTFIX for the similar reason:
4.9 and 5 don't have the resp. bug, all 4.8.x have.


  parent reply	other threads:[~2015-02-11 20:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-07 14:23 [Bug web/64968] New: " LpSolit at netscape dot net
2015-02-07 14:44 ` [Bug web/64968] " trippels at gcc dot gnu.org
2015-02-09 10:39 ` LpSolit at netscape dot net
2015-02-09 11:43 ` fche at redhat dot com
2015-02-11 14:37 ` LpSolit at netscape dot net
2015-02-11 16:33 ` fche at redhat dot com
2015-02-11 20:46 ` LpSolit at netscape dot net [this message]
2015-02-11 20:48 ` LpSolit at netscape dot net
2015-04-18 18:30 ` LpSolit at netscape dot net
2015-04-27 15:13 ` mikael at gcc dot gnu.org
2015-04-27 17:39 ` fche at redhat dot com
2015-04-27 18:34 ` LpSolit at netscape dot net
2015-04-27 19:47 ` LpSolit at netscape dot net
2015-04-28 16:28 ` trippels at gcc dot gnu.org
2015-04-28 18:26 ` LpSolit at netscape dot net
2015-04-29 12:27 ` LpSolit at netscape dot net
2015-04-29 16:02 ` trippels at gcc dot gnu.org
2015-04-30 13:48 ` trippels at gcc dot gnu.org
2015-04-30 16:34 ` LpSolit at netscape dot net
2015-04-30 20:53 ` LpSolit at netscape dot net
2015-05-01  9:16 ` LpSolit at netscape dot net
2015-05-03  1:00 ` LpSolit at netscape dot net
2015-05-08  6:22 ` trippels at gcc dot gnu.org
2015-05-08  6:46 ` schwab@linux-m68k.org
2015-05-08  6:51 ` trippels at gcc dot gnu.org
2015-05-08 11:02 ` LpSolit at netscape dot net
2015-05-08 18:55 ` LpSolit at netscape dot net
2015-05-08 19:04 ` trippels at gcc dot gnu.org
2015-05-15 14:06 ` LpSolit at netscape dot net
2015-05-26 14:15 ` trippels at gcc dot gnu.org
2015-05-26 17:41 ` fche at redhat dot com
2015-07-13 10:49 ` trippels at gcc dot gnu.org
2015-09-25  9:05 ` trippels at gcc dot gnu.org
2015-09-26 15:28 ` LpSolit at netscape dot net

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-64968-4-NsrBoHVAAP@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).