public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: joel@OARcorp.com To: gcc-gnats@gcc.gnu.org Subject: bootstrap/3266: gthr-rtems.h bug impacts *-rtems Date: Tue, 19 Jun 2001 11:36:00 -0000 [thread overview] Message-ID: <20010619183527.17698.qmail@sourceware.cygnus.com> (raw) >Number: 3266 >Category: bootstrap >Synopsis: gthr-rtems.h bug impacts *-rtems >Confidential: no >Severity: critical >Priority: high >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Jun 19 11:36:02 PDT 2001 >Closed-Date: >Last-Modified: >Originator: joel@OARcorp.com >Release: gcc 3.0 (patch versus 20010614) >Organization: >Environment: GNU/Linux x86 (RedHat 6.x host) targeting any *-rtems that is stable enough to try to build C++ >Description: rtems is not in the switch in gcc/configure.in so you can't enable rtems threading. And gthr-rtems.h was missing a required function. >How-To-Repeat: Build i386 or sparc-rtems and with --enable-threads=rtems and it will die in gthr-rtems.h. >Fix: Attached. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="gcc-rtems_thread.patch" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="gcc-rtems_thread.patch" MjAwMS0wNi0xOQlKb2VsIFNoZXJyaWxsIDxqb2VsQE9BUmNvcnAuY29tPgoKCSogY29uZmlndXJl LmluOiBBZGQgcnRlbXMgYXMgYSBzdXBwb3J0ZWQgdGhyZWFkIG1vZGVsLgoJKiBndGhyLXJ0ZW1z Lmg6IEFkZCBtaXNzaW5nIGVudHJ5IHBvaW50IF9fZ3RocmVhZF9hY3RpdmVfcC4KCmRpZmYgLXVO ciAvdXNyMS9ydGVtcy93b3JrLXRvb2xzL29yaWdpbmFsL2djYy0zLjAtMjAwMTA2MTQvZ2NjL2Nv bmZpZ3VyZS5pbiBnY2MtMy4wLTIwMDEwNjE0L2djYy9jb25maWd1cmUuaW4KLS0tIC91c3IxL3J0 ZW1zL3dvcmstdG9vbHMvb3JpZ2luYWwvZ2NjLTMuMC0yMDAxMDYxNC9nY2MvY29uZmlndXJlLmlu CVR1ZSBKdW4gMTIgMjE6Mjc6NTggMjAwMQorKysgZ2NjLTMuMC0yMDAxMDYxNC9nY2MvY29uZmln dXJlLmluCUZyaSBKdW4gMTUgMTE6MDM6MDcgMjAwMQpAQCAtMjg4LDcgKzI4OCw3IEBACiAJCXRh cmdldF90aHJlYWRfZmlsZT0nJwogCQk7OwogCXhkZWNvc2YxIHwgeGlyaXggfCB4bWFjaCB8IHhv czIgfCB4cG9zaXggfCB4cHRocmVhZHMgfCB4c2luZ2xlIHwgXAotCXhzb2xhcmlzIHwgeHdpbjMy IHwgeGRjZSB8IHh2eHdvcmtzIHwgeGFpeCkKKwl4c29sYXJpcyB8IHh3aW4zMiB8IHhkY2UgfCB4 cnRlbXN8IHh2eHdvcmtzIHwgeGFpeCkKIAkJdGFyZ2V0X3RocmVhZF9maWxlPSRlbmFibGVfdGhy ZWFkc19mbGFnCiAJCTs7CiAJKikKZGlmZiAtdU5yIC91c3IxL3J0ZW1zL3dvcmstdG9vbHMvb3Jp Z2luYWwvZ2NjLTMuMC0yMDAxMDYxNC9nY2MvZ3Roci1ydGVtcy5oIGdjYy0zLjAtMjAwMTA2MTQv Z2NjL2d0aHItcnRlbXMuaAotLS0gL3VzcjEvcnRlbXMvd29yay10b29scy9vcmlnaW5hbC9nY2Mt My4wLTIwMDEwNjE0L2djYy9ndGhyLXJ0ZW1zLmgJV2VkIERlYyAgNiAyMDo0MjowMSAyMDAwCisr KyBnY2MtMy4wLTIwMDEwNjE0L2djYy9ndGhyLXJ0ZW1zLmgJTW9uIEp1biAxOCAxMDoyNjo1OCAy MDAxCkBAIC02Miw2ICs2MiwxMyBAQAogZXh0ZXJuIGludCBydGVtc19neHhfbXV0ZXhfdW5sb2Nr IChfX2d0aHJlYWRfbXV0ZXhfdCAqbXV0ZXgpOwogCiAKKy8qIFJURU1TIHRocmVhZGluZyBpcyBh bHdheXMgYWN0aXZlICovCitzdGF0aWMgaW5saW5lIGludAorX19ndGhyZWFkX2FjdGl2ZV9wICh2 b2lkKQoreworICByZXR1cm4gMTsKK30KKwogLyogV3JhcHBlciBjYWxscyAqLwogc3RhdGljIGlu bGluZSBpbnQKIF9fZ3RocmVhZF9vbmNlIChfX2d0aHJlYWRfb25jZV90ICpvbmNlLCB2b2lkICgq ZnVuYykgKCkpCg==
next reply other threads:[~2001-06-19 11:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-19 11:36 joel [this message] 2001-06-21 14:20 ljrittle 2001-07-30 8:42 ljrittle
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=20010619183527.17698.qmail@sourceware.cygnus.com \ --to=joel@oarcorp.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: linkBe 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).