public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65548] [5/6 Regression] gfc_conv_procedure_call
Date: Tue, 05 May 2015 12:43:00 -0000	[thread overview]
Message-ID: <bug-65548-4-ByfKD6R113@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65548-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #37 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to vehre from comment #36)
> I am waiting for an official review of the patch, to be allowed to commit to
> trunk. So I am not waiting on you. :-)

I see. Got it. :D
>From gcc-bugs-return-485515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 05 13:04:49 2015
Return-Path: <gcc-bugs-return-485515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64091 invoked by alias); 5 May 2015 13:04:49 -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 64030 invoked by uid 48); 5 May 2015 13:04:45 -0000
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/16351] NULL dereference warnings
Date: Tue, 05 May 2015 13:04: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.0.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: manu at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16351-4-TJHHuyuT5l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-16351-4@http.gcc.gnu.org/bugzilla/>
References: <bug-16351-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: 2015-05/txt/msg00355.txt.bz2
Content-length: 1067

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

--- Comment #24 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Tim Ruehsen from comment #23)

> The requested warning is an absolutely must-have (enabled by default).
> Seeing this bug open since 2004 is... well ... I have no words.

GCC needs lots of more developers. Not "experts" or "hackers", but simply
people with some patience and curiosity and basic knowledge about C/C++ and
compiling and debugging code in GNU/Linux. We need people that can focus on
things like this for a couple of hours every week for months and get it done
from start to finish.

Paid developers are paid to work on other things (targets, optimizations,
extensions) and rarely have the time and focus necessary to get projects like
this finished. Volunteers are few and we already have our hands very full with
our own little projects.

I can give you many examples of old "must-have" bugs that are "easy" to fix,
but simply there is no one with enough time and motivation to get them done.
>From gcc-bugs-return-485516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 05 13:16:17 2015
Return-Path: <gcc-bugs-return-485516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110842 invoked by alias); 5 May 2015 13:16:17 -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 110795 invoked by uid 48); 5 May 2015 13:16:13 -0000
From: "green at moxielogic dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/66018] New: opendir configure test not working when GCC_NO_EXECUTABLES
Date: Tue, 05 May 2015 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: green at moxielogic dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
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 target_milestone
Message-ID: <bug-66018-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-05/txt/msg00356.txt.bz2
Content-length: 676

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

            Bug ID: 66018
           Summary: opendir configure test not working when
                    GCC_NO_EXECUTABLES
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: green at moxielogic dot com
  Target Milestone: ---

I'm building a moxie-elf toolchain, which defines GCC_NO_EXECUTABLES during
part of the build process.

The new filesystem-ts code forces an opendir configure test that fails when
GCC_NO_EXECUTABLES is defined.


  parent reply	other threads:[~2015-05-05 12:43 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25  7:11 [Bug fortran/65548] New: [5.0 " juergen.reuter at desy dot de
2015-03-25  7:15 ` [Bug fortran/65548] " juergen.reuter at desy dot de
2015-03-25  9:03 ` [Bug fortran/65548] [5 " jakub at gcc dot gnu.org
2015-03-25  9:03 ` dominiq at lps dot ens.fr
2015-03-27 13:47 ` dominiq at lps dot ens.fr
2015-04-07 14:11 ` vehre at gcc dot gnu.org
2015-04-09  8:26 ` vehre at gcc dot gnu.org
2015-04-10  7:19 ` juergen.reuter at desy dot de
2015-04-10 13:48 ` dominiq at lps dot ens.fr
2015-04-10 13:50 ` juergen.reuter at desy dot de
2015-04-10 16:48 ` juergen.reuter at desy dot de
2015-04-15 10:06 ` [Bug fortran/65548] [5/6 " vehre at gcc dot gnu.org
2015-04-15 12:48 ` juergen.reuter at desy dot de
2015-04-15 13:03 ` dominiq at lps dot ens.fr
2015-04-17 16:17 ` juergen.reuter at desy dot de
2015-04-17 16:31 ` dominiq at lps dot ens.fr
2015-04-22 12:02 ` jakub at gcc dot gnu.org
2015-04-23 12:51 ` vehre at gcc dot gnu.org
2015-04-23 12:54 ` juergen.reuter at desy dot de
2015-04-23 13:02 ` juergen.reuter at desy dot de
2015-04-23 13:22 ` dominiq at lps dot ens.fr
2015-04-23 13:52 ` juergen.reuter at desy dot de
2015-04-23 15:06 ` juergen.reuter at desy dot de
2015-04-23 15:11 ` dominiq at lps dot ens.fr
2015-04-28 21:55 ` vehre at gcc dot gnu.org
2015-04-28 22:40 ` juergen.reuter at desy dot de
2015-04-29  8:01 ` vehre at gcc dot gnu.org
2015-04-29  8:06 ` juergen.reuter at desy dot de
2015-04-29  8:33 ` vehre at gcc dot gnu.org
2015-04-29 13:19 ` juergen.reuter at desy dot de
2015-05-05  9:12 ` vehre at gcc dot gnu.org
2015-05-05  9:36 ` juergen.reuter at desy dot de
2015-05-05 10:15 ` vehre at gcc dot gnu.org
2015-05-05 12:43 ` juergen.reuter at desy dot de [this message]
2015-05-20 14:57 ` vehre at gcc dot gnu.org
2015-05-29  9:06 ` vehre at gcc dot gnu.org

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-65548-4-ByfKD6R113@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).