public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gregod@cs.rpi.edu
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/5506: Include of <valarray> fails on FreeBSD 3.4 due to use of _T identifier
Date: Sun, 27 Jan 2002 06:46:00 -0000 [thread overview]
Message-ID: <20020127143747.1082.qmail@sources.redhat.com> (raw)
>Number: 5506
>Category: libstdc++
>Synopsis: Include of <valarray> fails on FreeBSD 3.4 due to use of _T identifier
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jan 27 06:46:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Doug Gregor
>Release: gcc-2.95.x (also verified on 2.95 branch of CVS)
>Organization:
>Environment:
FreeBSD 3.4
>Description:
FreeBSD 3.4's <ctype.h> defines a macro _T. Then when _T is used as a template parameter (in include/g++-3/std/mask_array.h and /include/g++-3/std/slice_array.h), it is expanded to an implementation-defined constant and bad things happen.
>How-To-Repeat:
#include <valarray>
>Fix:
sed s/_T/T/g on slice_array.h and mask_array.h
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-01-27 14:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-27 6:46 gregod [this message]
2002-01-27 7:45 paolo
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=20020127143747.1082.qmail@sources.redhat.com \
--to=gregod@cs.rpi.edu \
--cc=gcc-gnats@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).