public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: warren.dodge@tektronix.com
To: gcc-gnats@gcc.gnu.org
Subject: c/10302: Certain -D values cause gcc to issue strange errors
Date: Thu, 03 Apr 2003 04:46:00 -0000	[thread overview]
Message-ID: <20030403044347.6747.qmail@sources.redhat.com> (raw)


>Number:         10302
>Category:       c
>Synopsis:       Certain -D values cause gcc to issue strange errors
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 03 04:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Warren Dodge
>Release:        gcc-3.2.2
>Organization:
>Environment:
Solaris 2.5.1 or Solaris 8
>Description:
Attached is a command line and test.c file which shows a strange error in gcc-3.2.2

gcc-3.2.1 compiles just fine.

>How-To-Repeat:
Just run the gcc command on test.v
>Fix:
No idea.
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/sh; name="test.sh"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="test.sh"

I1RoaXMgaXMgdGhlIHNjcmlwdCB3ZSB1c2UgdG8gcnVuIDMuMi4xIGFuZCAzLjIuMgojISAvYmlu
L3NoCmVjaG8gIkJhZCBnY2MiCi9wcm9qL2FkZy9nbnV0b29scy9iaW4vZ2NjIC1XYWxsIC1PMyAt
ZlBJQyAtREJVSUxEX0RBVEU9JyJXZWQgQXByICAyIDE3OjAxOjQwIFBTVCAyMDAzIicgLURDQ19W
RVJTSU9OPSciZ2NjIChHQ0MpIDMuMi4yIicgLURCVUlMRF9ESVI9JyIvbG9naW4vc3Rvbnl5L2xv
Y2FsL3Vzci9kcmlsbFN0ciInIC1jIC1vIHRlc3QubyB0ZXN0LmMKZWNobyAiZ29vZCBnY2MiCi9w
cm9qL3dkdC8kQVJDSC9iaW4vZ2NjIC1XYWxsIC1PMyAtZlBJQyAtREJVSUxEX0RBVEU9JyJXZWQg
QXByICAyIDE3OjAxOjQwIFBTVCAyMDAzIicgLURDQ19WRVJTSU9OPSciZ2NjIChHQ0MpIDMuMi4x
IicgLURCVUlMRF9ESVI9JyIvbG9naW4vc3Rvbnl5L2xvY2FsL3Vzci9kcmlsbFN0ciInIC1jIC1v
IHRlc3QubyB0ZXN0LmMKCgpUaGlzIGlzIHRlc3QuYwpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwojaW5j
bHVkZSA8c3RkbGliLmg+CiNpbmNsdWRlIDxzdGRpby5oPgoKaW50IG1haW4gKGludCBhcmdjLCBj
aGFyICoqYXJndikKewogICBwcmludGYgKCJIZWxsbyBXb3JsZFxuIik7CiAgIHByaW50ZiAoIkJV
SUxEX0RBVEU6ICAiKTsKICAgcHJpbnRmIChCVUlMRF9EQVRFKTsKICAgcHJpbnRmICgiXG4iKTsK
ICAgcHJpbnRmICgiQ0NfVkVSU0lPTjogICIpOwogICBwcmludGYgKENDX1ZFUlNJT04pOwogICBw
cmludGYgKCJcbiIpOwogICBwcmludGYgKCJCVUlMRF9ESVI6ICAiKTsKICAgcHJpbnRmIChCVUlM
RF9ESVIpOwogICBwcmludGYgKCJcbiIpOwp9Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCgpUaGlzIGlz
IHRoZSBlcnJvciBmcm9tIGdjYy0zLjIuMgoKZ2NjOiBjYW5ub3Qgc3BlY2lmeSAtbyB3aXRoIC1j
IG9yIC1TIGFuZCBtdWx0aXBsZSBjb21waWxhdGlvbnMKCg==


                 reply	other threads:[~2003-04-03  4:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030403044347.6747.qmail@sources.redhat.com \
    --to=warren.dodge@tektronix.com \
    --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).