public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Servatius.Brandt@fujitsu-siemens.com To: gcc-gnats@gcc.gnu.org Cc: Joachim.Canisius@fujitsu-siemens.com, Erwin.Unruh@fujitsu-siemens.com, Heinrich.Brand@fujitsu-siemens.com Subject: c/6348: internal error in allocate_dynamic_stack_space with STACK_SIZE_MODE non-default Date: Thu, 18 Apr 2002 03:06:00 -0000 [thread overview] Message-ID: <20020418095654.30223.qmail@sources.redhat.com> (raw) >Number: 6348 >Category: c >Synopsis: internal error in allocate_dynamic_stack_space with STACK_SIZE_MODE non-default >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Apr 18 03:06:28 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Servatius.Brandt@fujitsu-siemens.com >Release: gcc-3.0.4 >Organization: >Environment: all ports providing an allocate_stack pattern with STACK_SIZE_MODE >Description: There is an internal error in allocate_dynamic_stack_space() in explow.c. It appears when an allocate_stack pattern is provided in the machine description, so that HAVE_allocate_stack gets #defined, and when STACK_SIZE_MODE is different from Pmode. Reason is that the size argument of allocate_dynamic_stack_space() is converted to Pmode at the beginning, so that the copy_to_mode_reg of size to a register of mode STACK_SIZE_MODE fails. A bug fix converting size to STACK_SIZE_MODE and using copy_to_reg then is included. >How-To-Repeat: Any port providing allocate_stack in the machine description and using STACK_SIZE_MODE of a size different from Pmode. >Fix: See file attachment. >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="explow.c.fix"; name="explow.c.fix" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="explow.c.fix" KioqIGV4cGxvdy5jCVRodSBBcHIgMTggMTE6MzA6MjIgMjAwMgotLS0gZXhwbG93LmMubmV3CVRo dSBBcHIgMTggMTE6MzE6MDUgMjAwMgoqKioqKioqKioqKioqKioKKioqIDE0MjYsMTQzMiAqKioq CiAgCiAgICAgICAgcHJlZCA9IGluc25fZGF0YVsoaW50KSBDT0RFX0ZPUl9hbGxvY2F0ZV9zdGFj a10ub3BlcmFuZFsxXS5wcmVkaWNhdGU7CiAgICAgICAgaWYgKHByZWQgJiYgISAoKCpwcmVkKSAo c2l6ZSwgbW9kZSkpKQohIAlzaXplID0gY29weV90b19tb2RlX3JlZyAobW9kZSwgc2l6ZSk7CiAg CiAgICAgICAgZW1pdF9pbnNuIChnZW5fYWxsb2NhdGVfc3RhY2sgKHRhcmdldCwgc2l6ZSkpOwog ICAgICB9Ci0tLSAxNDI2LDE0MzIgLS0tLQogIAogICAgICAgIHByZWQgPSBpbnNuX2RhdGFbKGlu dCkgQ09ERV9GT1JfYWxsb2NhdGVfc3RhY2tdLm9wZXJhbmRbMV0ucHJlZGljYXRlOwogICAgICAg IGlmIChwcmVkICYmICEgKCgqcHJlZCkgKHNpemUsIG1vZGUpKSkKISAJc2l6ZSA9IGNvcHlfdG9f cmVnIChjb252ZXJ0X3RvX21vZGUgKG1vZGUsIHNpemUsIDEpKTsKICAKICAgICAgICBlbWl0X2lu c24gKGdlbl9hbGxvY2F0ZV9zdGFjayAodGFyZ2V0LCBzaXplKSk7CiAgICAgIH0K
reply other threads:[~2002-04-18 10:06 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=20020418095654.30223.qmail@sources.redhat.com \ --to=servatius.brandt@fujitsu-siemens.com \ --cc=Erwin.Unruh@fujitsu-siemens.com \ --cc=Heinrich.Brand@fujitsu-siemens.com \ --cc=Joachim.Canisius@fujitsu-siemens.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).