public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org
To: d@openbsd.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
nobody@gcc.gnu.org
Subject: Re: debug/2283: -g3 -O1 -finline-function and __attribute__((constructor)) yield bad stabs
Date: Sun, 17 Mar 2002 18:37:00 -0000 [thread overview]
Message-ID: <20020318023703.22812.qmail@sources.redhat.com> (raw)
Synopsis: -g3 -O1 -finline-function and __attribute__((constructor)) yield bad stabs
State-Changed-From-To: open->feedback
State-Changed-By: rodrigc
State-Changed-When: Sun Mar 17 18:37:03 2002
State-Changed-Why:
Cannot reproduce your problem with gcc 3.0.4
or the latest gcc 3.1 pre-release snapshot, under Linux.
Is this still a problem under OpenBSD?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=2283
next reply other threads:[~2002-03-18 2:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 18:37 rodrigc [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-18 5:06 rodrigc
2002-03-18 4:56 David Leonard
2001-04-01 0:00 d
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=20020318023703.22812.qmail@sources.redhat.com \
--to=rodrigc@gcc.gnu.org \
--cc=d@openbsd.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).