public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rschiele at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/30460] [4.0/4.1/4.2/4.3 Regression] asm_debug is not initialized in gcc.c when using a "default" specs file
Date: Sun, 14 Jan 2007 08:03:00 -0000 [thread overview]
Message-ID: <20070114080324.2089.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30460-646@http.gcc.gnu.org/bugzilla/>
------- Comment #6 from rschiele at gmail dot com 2007-01-14 08:03 -------
Agreed, but why shouldn't we change the special handling of the default specs
file as suggested in comment #4? I can't see why we should enforce people to
specify _full_ information in the default specs file if they only want to
change _one_ thing from the compiled-in values. Is there any reason?
As far as I can see my suggestion in comment #4 would solve this issue and make
usage of a default specs file more convenient.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30460
next prev parent reply other threads:[~2007-01-14 8:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-14 1:52 [Bug driver/30460] New: asm_debug is not initialized in gcc.c rschiele at uni-mannheim dot de
2007-01-14 1:56 ` [Bug driver/30460] " rschiele at uni-mannheim dot de
2007-01-14 2:10 ` pinskia at gcc dot gnu dot org
2007-01-14 2:22 ` rschiele at gmail dot com
2007-01-14 2:49 ` [Bug driver/30460] [4.0/4.1/4.2/4.3 Regression] asm_debug is not initialized in gcc.c when using a specs file pinskia at gcc dot gnu dot org
2007-01-14 3:12 ` rschiele at gmail dot com
2007-01-14 6:16 ` [Bug driver/30460] [4.0/4.1/4.2/4.3 Regression] asm_debug is not initialized in gcc.c when using a "default" " pinskia at gcc dot gnu dot org
2007-01-14 8:03 ` rschiele at gmail dot com [this message]
2007-01-14 13:52 ` rschiele at gmail dot com
2007-02-03 21:24 ` gdr at gcc dot gnu dot org
2007-02-03 21:25 ` pinskia at gcc dot gnu dot org
2007-02-05 5:52 ` mmitchel at gcc dot gnu dot org
2007-02-14 9:26 ` mmitchel at gcc dot gnu dot org
2007-10-27 21:07 ` aldyh at gcc dot gnu dot org
2007-11-16 7:03 ` jakub at gcc dot gnu dot org
2007-11-16 7:11 ` [Bug driver/30460] [4.0/4.1/4.2 " jakub at gcc dot gnu dot org
2008-07-04 21:49 ` [Bug driver/30460] [4.2 " jsm28 at gcc dot gnu dot org
2009-03-30 20:22 ` jsm28 at gcc dot gnu dot 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=20070114080324.2089.qmail@sourceware.org \
--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).