public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aran at 100acres dot us" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39570] cabs and cabsf are named differently on NetBSD 5
Date: Sat, 28 Mar 2009 18:14:00 -0000 [thread overview]
Message-ID: <20090328181352.7393.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39570-15541@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from aran at 100acres dot us 2009-03-28 18:13 -------
(In reply to comment #5)
> Another fix is to #undef TARGET_C99_FUNCTIONS as obviously netbsd is another
> OS without a clue ...
>
Please explain how an OS with a clue would handle this problem. Older binaries
that use the pre-c99 complex structure links to the existing linker symbols,
cabs and cabsf. Changing the meaning of these symbols to the c99 meaning would
break these legacy programs. It seems cluefull to decorate these symbols with
__c99_ and provide a rename in the header. What would be a better solution?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39570
next prev parent reply other threads:[~2009-03-28 18:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-28 0:17 [Bug fortran/39570] New: " aran at 100acres dot us
2009-03-28 0:22 ` [Bug fortran/39570] " aran at 100acres dot us
2009-03-28 0:23 ` aran at 100acres dot us
2009-03-28 1:03 ` steven at gcc dot gnu dot org
2009-03-28 1:35 ` aran at 100acres dot us
2009-03-28 9:54 ` rguenth at gcc dot gnu dot org
2009-03-28 13:09 ` [Bug target/39570] " fxcoudert at gcc dot gnu dot org
2009-03-28 18:14 ` aran at 100acres dot us [this message]
2009-03-28 18:30 ` jakub at gcc dot gnu dot org
2009-03-28 19:39 ` aran at 100acres dot us
[not found] <bug-39570-4@http.gcc.gnu.org/bugzilla/>
2011-02-21 9:50 ` burnus at gcc dot gnu.org
2011-02-22 13:42 ` burnus at gcc dot gnu.org
2011-11-07 13:00 ` fxcoudert at gcc dot gnu.org
2014-12-17 22:04 ` kuehro at gmx dot de
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=20090328181352.7393.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).