public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: johannes-peter.schneider@sysde.eads.net
To: gcc-gnats@gcc.gnu.org
Subject: ada/5346: GCC3.1(20020107) Internal compiler error in output_constant.
Date: Thu, 10 Jan 2002 04:46:00 -0000	[thread overview]
Message-ID: <20020110124544.18359.qmail@sources.redhat.com> (raw)


>Number:         5346
>Category:       ada
>Synopsis:       GCC3.1(20020107) Internal compiler error in output_constant.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 10 04:46:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     johannes-peter.schneider@sysde.eads.net
>Release:        gcc version 3.1 20020107 (experimental)
>Organization:
>Environment:
SuSE Linux 7.3 Kernel 2.4.10 Platform i686-pc-linux-gnu
>Description:
+=====GNAT BUG DETECTED==============================+
| 5.00w (20010924) (i686-pc-linux-gnu) GCC error: | Internal compiler error in output_constant, at varasm.c:4487             
Error detected at standard_types.ads:110:61                
gcc command entered:  gcc -c standard_types.adb
+==================================================+
>How-To-Repeat:
compile attached sources
>Fix:
no fix yet
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-tbz; name="bugdata.tar.bz2"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bugdata.tar.bz2"

QlpoOTFBWSZTWeMzPjwABWJ/ju5USsBo53/bP+/fIP/v3/AAAIABAAgACFAEnuSIG1tsAAQkU1U9
T1NNNqGgAAAADQeoBoyGgAA4yNMmJoMmTCaZAyGgNAaZNDACaAwzSgqfoqPUMgaDQAPUBiBoA9QD
QAA4yNMmJoMmTCaZAyGgNAaZNDACaAwkSCCEYFPTKn5E2piTaMpp6ag9QAeoGNRmmU9x+Hu1F8Hi
hEVAAfFTNsOJSh+WkFFYDQhoTIA0n1MMSzkgnBQfrFWigNVSEMQ2G/plEVakErqCFBAIQ0IWlJLo
roPjYUXgYBIMQwQu5pAmMEFzQklTQ0cjQquGkATDt74FvsOi03ydYiUKMcHbirnDQo9OZr0Q4Ij4
H0Wik5G/Xhu2ha3zUwYqqXdyOswRfYs3sLCpRbqEKaNfY4jsrXgAUzrrAFbUXFLcKFpeXpQDKtQY
FKgPDjpVGHJhfpcvk5VToVWvLEElhnE8WeRSSwosyWSGWBb+5GViDAr+AvGEiHBbJsLcI5EQRD0R
WeimNcGrlxawYYhHE+rETPZTdULFubYqqXs67DYRMMDDeEy8m/0JkyxkF8MooT5i1RIKEzAOhBTE
QQTLYJk4KUe/OVMkrG2c8XqtxBBFAAybFq1xwytztz0k9RbKJW7CdtziMEXMtuurErnE4jiQYQFn
3IFbp5riW/SSsVJGemhTUkXSUcbcrU8ifpYnbssgqxIS9F5mhA3CEFqkbCjtqE8hKokaqa1EwsTW
nUoqwBIFAy1HZYuEwqxN3wSFgNUQT58NCYMaEwW9YazjDuEvMcanMXectB5qi+qqql5ICLXpWSDu
95TCN5Cz6d9p5WiIBlJG8klZGMax0fJyXzrnstAq7hUEw8w8hKFQKvtDHcLyHAjQK4yBbhDN8DZ8
QuW1SWg60TTJWiJmZEQkQiIGBAoFOyqY1BIi/T8Q6jZNscjNBInQG0myjkmR8icUTrIo2N6TCVS1
BAjeEUESDv1lgtvKL5I702vMAauBdCh9pmLmDym+BlabxHPlG1yrOuMWszm1GP32kd1RcIyYvagf
SEgDaj0gGhB6sNhnTCchZji/2SQXomr1pJCUDQRZZaOJSUSk4uSmpC3lExLzMmuRLdDVFUxioZNM
3lVRXjk0DJCYTKk0ihIXrMhAFwB13tSEu9B0oLZUKNdSWg9GZG1NekW6+09pr8ukgQz13rYg5SxC
OQQwXYas48QxazUEhExM86JIfwigE6mTRtISNLV556qIcgkJkiQ5BNO0muBpwdhqVC6FUwnj4waL
j0BzF66HjY6xeidOYKwMdFNE16iZjUywUkDLRXHCVWA8AwrCmqnGxjbR2CwBoWBL3m41G4oms54H
ic5vgcK6QBoPIFyvoXyEmgY0wrmCgX+LuSKcKEhxmZ8eAA==


             reply	other threads:[~2002-01-10 12:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  4:46 johannes-peter.schneider [this message]
2003-05-10 21:26 Dara Hazeghi
2003-05-12  8:36 Dara Hazeghi
2003-05-12 11:20 giovannibajo

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=20020110124544.18359.qmail@sources.redhat.com \
    --to=johannes-peter.schneider@sysde.eads.net \
    --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).