public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: tilps@hotmail.com
To: gcc-gnats@gcc.gnu.org
Subject: bootstrap/10051: bootstrap failure in 3.4 due to bad FDR initialiser in mips-tfile for alpha.
Date: Wed, 12 Mar 2003 23:46:00 -0000 [thread overview]
Message-ID: <20030312234259.8873.qmail@sources.redhat.com> (raw)
>Number: 10051
>Category: bootstrap
>Synopsis: bootstrap failure in 3.4 due to bad FDR initialiser in mips-tfile for alpha.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Mar 12 23:46:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: tilps@hotmail.com
>Release: 3.4 CVS - 12/03/2003
>Organization:
>Environment:
alpha OSF1 4.0d
building using gcc 3.3 20021102
>Description:
During stage 2 - compile fails due to enabling of -Werror.
However the warnings are indicitive of a real problem.
Comparison between initialiser comments and the system's sym.h header file reveal 2 issues - first the (I assume accidental) repetition of the lineoffset and line members - and the incorrect ordering of the fTrim member.
The fact that bootstrap fails is a regression, but I wonder if the issue has just been hidden in the past due to lack of -Werror - since i've had several issues which seemed possibly mips-tfile related.
>How-To-Repeat:
make bootstrap
wait. :)
>Fix:
see attached patch (trivial enough I hope :P)
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="mips-tfile.patch"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="mips-tfile.patch"
SW5kZXg6IG1pcHMtdGZpbGUuYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvY3Zzcm9vdC9nY2MvZ2Nj
L2djYy9taXBzLXRmaWxlLmMsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEuNTAKZGlmZiAtYyAtMyAt
cCAtcjEuNTAgbWlwcy10ZmlsZS5jCioqKiBtaXBzLXRmaWxlLmMJMTEgRmViIDIwMDMgMDM6NDc6
NDggLTAwMDAJMS41MAotLS0gbWlwcy10ZmlsZS5jCTEyIE1hciAyMDAzIDIzOjI0OjU0IC0wMDAw
CioqKioqKioqKioqKioqKiBzdGF0aWMgZWZkcl90IGluaXRfZmlsZSA9IAoqKiogMTA5NiwxMTA2
ICoqKioKICAjZWxzZQogICAgICAwLAkJCS8qIGZCaWdlbmRpYW46CWlmIDEsIGNvbXBpbGVkIG9u
IGJpZyBlbmRpYW4gbWFjaGluZSAqLwogICNlbmRpZgotICAgICAwLAkJCS8qIGZUcmltOgl3aGV0
aGVyIHRoZSBzeW1ib2wgdGFibGUgd2FzIHRyaW1tZWQgKi8KICAgICAgR0xFVkVMXzIsCQkvKiBn
bGV2ZWw6CWxldmVsIHRoaXMgZmlsZSB3YXMgY29tcGlsZWQgd2l0aCAqLwogICAgICAwLAkJCS8q
IHJlc2VydmVkOglyZXNlcnZlZCBmb3IgZnV0dXJlIHVzZSAqLwotICAgICAwLAkJCS8qIGNiTGlu
ZU9mZnNldDogYnl0ZSBvZmZzZXQgZnJvbSBoZWFkZXIgZm9yIHRoaXMgZmlsZSBsbidzICovCi0g
ICAgIDAsCQkJLyogY2JMaW5lOglzaXplIG9mIGxpbmVzIGZvciB0aGlzIGZpbGUgKi8KICAjZWxz
ZQogICAgICAwLAkJCS8qIGFkcjoJCW1lbW9yeSBhZGRyZXNzIG9mIGJlZ2lubmluZyBvZiBmaWxl
ICovCiAgICAgIDAsCQkJLyogcnNzOgkJZmlsZSBuYW1lIChvZiBzb3VyY2UsIGlmIGtub3duKSAq
LwotLS0gMTA5NiwxMTA0IC0tLS0KICAjZWxzZQogICAgICAwLAkJCS8qIGZCaWdlbmRpYW46CWlm
IDEsIGNvbXBpbGVkIG9uIGJpZyBlbmRpYW4gbWFjaGluZSAqLwogICNlbmRpZgogICAgICBHTEVW
RUxfMiwJCS8qIGdsZXZlbDoJbGV2ZWwgdGhpcyBmaWxlIHdhcyBjb21waWxlZCB3aXRoICovCisg
ICAgIDAsCQkJLyogZlRyaW06CXdoZXRoZXIgdGhlIHN5bWJvbCB0YWJsZSB3YXMgdHJpbW1lZCAq
LwogICAgICAwLAkJCS8qIHJlc2VydmVkOglyZXNlcnZlZCBmb3IgZnV0dXJlIHVzZSAqLwogICNl
bHNlCiAgICAgIDAsCQkJLyogYWRyOgkJbWVtb3J5IGFkZHJlc3Mgb2YgYmVnaW5uaW5nIG9mIGZp
bGUgKi8KICAgICAgMCwJCQkvKiByc3M6CQlmaWxlIG5hbWUgKG9mIHNvdXJjZSwgaWYga25vd24p
ICovCg==
next reply other threads:[~2003-03-12 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 23:46 tilps [this message]
2003-03-29 0:36 sayle
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=20030312234259.8873.qmail@sources.redhat.com \
--to=tilps@hotmail.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).