public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: David Leonard <david.leonard@itee.uq.edu.au> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: debug/2283: -g3 -O1 -finline-function and __attribute__((constructor)) yield bad stabs Date: Mon, 18 Mar 2002 04:56:00 -0000 [thread overview] Message-ID: <20020318125602.19278.qmail@sources.redhat.com> (raw) The following reply was made to PR debug/2283; it has been noted by GNATS. From: David Leonard <david.leonard@itee.uq.edu.au> To: <rodrigc@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: debug/2283: -g3 -O1 -finline-function and __attribute__((constructor)) yield bad stabs Date: Mon, 18 Mar 2002 22:51:56 +1000 (EST) On 18 Mar 2002, rodrigc@gcc.gnu.org typed thusly: > Synopsis: -g3 -O1 -finline-function and __attribute__((constructor)) yield bad stabs > 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 yes it is still a problem with the gcc that ships with openbsd 3.0. with openbsd 2.8 (when i originally filed the bug report) they were using "gcc version 2.95.3 20010112 (prerelease)", and with 3.0 it is now "gcc version 2.95.3 20010125 (prerelease)" Here is that same compilation unit being compiled under openbsd3.0/i386 blackhole:/tmp$ gcc -v -c x.c -g3 -O1 -finline-functions Reading specs from /usr/lib/gcc-lib/i386-unknown-openbsd3.0/2.95.3/specs gcc version 2.95.3 20010125 (prerelease) /usr/lib/gcc-lib/i386-unknown-openbsd3.0/2.95.3/cpp0 -lang-c -v -D__GNUC__=2 -D__GNUC_MINOR__=95 -D__unix__ -D__i386__ -D__OpenBSD__ -D__unix__ -D__i386__ -D__OpenBSD__ -Asystem(unix) -Asystem(OpenBSD) -Acpu(i386) -Amachine(i386) -D__OPTIMIZE__ -g3 x.c /tmp/ccAr8120.i GNU CPP version 2.95.3 20010125 (prerelease) (80386, BSD syntax) #include "..." search starts here: #include <...> search starts here: /usr/include End of search list. The following default directories have been omitted from the search path: /usr/include/g++ End of omitted list. /usr/lib/gcc-lib/i386-unknown-openbsd3.0/2.95.3/cc1 /tmp/ccAr8120.i -quiet -dumpbase x.c -g3 -O1 -version -finline-functions -o /tmp/ccvx8120.s GNU C version 2.95.3 20010125 (prerelease) (i386-unknown-openbsd3.0) compiled by GNU C version 2.95.3 20010125 (prerelease). as -o x.o /tmp/ccvx8120.s /tmp/ccvx8120.s: Assembler messages: /tmp/ccvx8120.s:61: Error: Local symbol LBB3 never defined. /tmp/ccvx8120.s:61: Error: Local symbol LBE3 never defined. /tmp/ccvx8120.s:61: Fatal error:2 errors, 0 warnings, no object file generated. -- David Leonard David.Leonard@itee.uq.edu.au Dept of Inf. Tech. and Elec. Engg _ Ph:+61 404 844 850 The University of Queensland |+| http://www.itee.uq.edu.au/~leonard/ QLD 4072 AUSTRALIA ~` '~ B73CD65FBEF4C089B79A8EBADF1A932F13EA0FC8 I have some questions about your code - suggestions really, in the form of direct orders. - T Farnon
next reply other threads:[~2002-03-18 12:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-18 4:56 David Leonard [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-18 5:06 rodrigc 2002-03-17 18:37 rodrigc 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=20020318125602.19278.qmail@sources.redhat.com \ --to=david.leonard@itee.uq.edu.au \ --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: linkBe 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).