public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "karl at freefriends dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/48306] [4.4/4.5/4.6/4.7 Regression] presence of gcc subdir with . in PATH causes breakdown
Date: Mon, 19 Dec 2011 23:06:00 -0000	[thread overview]
Message-ID: <bug-48306-4-cD8sUyZXUV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48306-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48306

--- Comment #7 from karl at freefriends dot org 2011-12-19 22:59:37 UTC ---
I hope you will decide that robustness against the execution environment is
more important than a few milliseconds of runtime.  I wouldn't have reported it
if I hadn't actually run into it in the course of working with the new gcc and
been surprised.  It's not like I read the code and observed a theoretical bug
:).


  parent reply	other threads:[~2011-12-19 23:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-28  1:44 [Bug driver/48306] New: " karl at freefriends dot org
2011-03-28  9:45 ` [Bug driver/48306] " rguenth at gcc dot gnu.org
2011-03-28 22:25 ` karl at freefriends dot org
2011-03-29 10:23 ` rguenth at gcc dot gnu.org
2011-03-29 10:23 ` [Bug driver/48306] [4.3/4.4/4.5/4.6/4.7 Regression] " rguenth at gcc dot gnu.org
2011-04-10 10:45 ` rguenth at gcc dot gnu.org
2011-06-27 15:14 ` rguenth at gcc dot gnu.org
2011-12-19 20:10 ` [Bug driver/48306] [4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org
2011-12-19 23:06 ` karl at freefriends dot org [this message]
2012-01-02 22:18 ` jakub at gcc dot gnu.org
2012-01-02 22:21 ` [Bug driver/48306] [4.4/4.5/4.6 " jakub at gcc dot gnu.org
2012-02-09 17:17 ` jakub at gcc dot gnu.org
2012-02-09 21:33 ` [Bug driver/48306] [4.4/4.5 " jakub at gcc dot gnu.org
2012-03-13 16:56 ` [Bug driver/48306] [4.4 " jakub at gcc dot gnu.org
2012-08-16  7:00 ` jakub 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-48306-4-cD8sUyZXUV@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).