public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pmanolov@lnxw.com
To: gcc-gnats@gcc.gnu.org
Subject: c/4243: sig 11 when __attribute((regparm(3))) used for function pointers
Date: Wed, 05 Sep 2001 18:16:00 -0000	[thread overview]
Message-ID: <20010906011428.19009.qmail@sourceware.cygnus.com> (raw)

>Number:         4243
>Category:       c
>Synopsis:       sig 11 when __attribute((regparm(3))) used for function pointers
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 05 18:16:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Petko Manolov
>Release:        unknown-1.0
>Organization:
>Environment:
Debian Linux, gcc-2.95.4
>Description:
When used more than once on pointer to function with
__attribute___((regparm(3))) GCC exit with signal 11.
This is intended to be a i386 Linux 2.4 loadable module.
The bug appears only with gcc-2.95.x, gcc-2.96 and gcc-3.0.x
are OK.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="errors"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="errors"

UmVhZGluZyBzcGVjcyBmcm9tIC91c3IvbGliL2djYy1saWIvaTM4Ni1saW51eC8yLjk1LjQvc3Bl
Y3MKZ2NjIHZlcnNpb24gMi45NS40IDIwMDEwOTAyIChEZWJpYW4gcHJlcmVsZWFzZSkKIC91c3Iv
bGliL2djYy1saWIvaTM4Ni1saW51eC8yLjk1LjQvY3BwMCAtbGFuZy1jIC12IC1EX19HTlVDX189
MiAtRF9fR05VQ19NSU5PUl9fPTk1IC1EX19FTEZfXyAtRHVuaXggLURfX2kzODZfXyAtRGxpbnV4
IC1EX19FTEZfXyAtRF9fdW5peF9fIC1EX19pMzg2X18gLURfX2xpbnV4X18gLURfX3VuaXggLURf
X2xpbnV4IC1Bc3lzdGVtKHBvc2l4KSAtRF9fT1BUSU1JWkVfXyAtQWNwdShpMzg2KSAtQW1hY2hp
bmUoaTM4NikgLURpMzg2IC1EX19pMzg2IC1EX19pMzg2X18gLURfX0tFUk5FTF9fIHRtcC5jIHRt
cC5pCkdOVSBDUFAgdmVyc2lvbiAyLjk1LjQgMjAwMTA5MDIgKERlYmlhbiBwcmVyZWxlYXNlKSAo
aTM4NiBMaW51eC9FTEYpCiNpbmNsdWRlICIuLi4iIHNlYXJjaCBzdGFydHMgaGVyZToKI2luY2x1
ZGUgPC4uLj4gc2VhcmNoIHN0YXJ0cyBoZXJlOgogL3Vzci9sb2NhbC9pbmNsdWRlCiAvdXNyL2xp
Yi9nY2MtbGliL2kzODYtbGludXgvMi45NS40L2luY2x1ZGUKIC91c3IvaW5jbHVkZQpFbmQgb2Yg
c2VhcmNoIGxpc3QuClRoZSBmb2xsb3dpbmcgZGVmYXVsdCBkaXJlY3RvcmllcyBoYXZlIGJlZW4g
b21pdHRlZCBmcm9tIHRoZSBzZWFyY2ggcGF0aDoKIC91c3IvbGliL2djYy1saWIvaTM4Ni1saW51
eC8yLjk1LjQvLi4vLi4vLi4vLi4vaW5jbHVkZS9nKystMwogL3Vzci9saWIvZ2NjLWxpYi9pMzg2
LWxpbnV4LzIuOTUuNC8uLi8uLi8uLi8uLi9pMzg2LWxpbnV4L2luY2x1ZGUKRW5kIG9mIG9taXR0
ZWQgbGlzdC4KIC91c3IvbGliL2djYy1saWIvaTM4Ni1saW51eC8yLjk1LjQvY2MxIHRtcC5pIC1x
dWlldCAtZHVtcGJhc2UgdG1wLmMgLU8yIC12ZXJzaW9uIC1vIHRtcC5zCkdOVSBDIHZlcnNpb24g
Mi45NS40IDIwMDEwOTAyIChEZWJpYW4gcHJlcmVsZWFzZSkgKGkzODYtbGludXgpIGNvbXBpbGVk
IGJ5IEdOVSBDIHZlcnNpb24gMi45NS40IDIwMDEwOTAyIChEZWJpYW4gcHJlcmVsZWFzZSkuCmdj
YzogSW50ZXJuYWwgY29tcGlsZXIgZXJyb3I6IHByb2dyYW0gY2MxIGdvdCBmYXRhbCBzaWduYWwg
MTEK


             reply	other threads:[~2001-09-05 18:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-05 18:16 pmanolov [this message]
2002-03-24 18:18 rth
2002-06-19 10:16 mmitchel

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=20010906011428.19009.qmail@sourceware.cygnus.com \
    --to=pmanolov@lnxw.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).