public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "armcc2000 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/24675] Stack corruption in ARM arch. if 64bit variable is passed to a function of which the low 32 use the register and the up 32 use the stack
Date: Thu, 10 Nov 2005 01:25:00 -0000	[thread overview]
Message-ID: <20051110012508.6717.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24675-11653@http.gcc.gnu.org/bugzilla/>



------- Comment #9 from armcc2000 at yahoo dot com  2005-11-10 01:25 -------
(In reply to comment #8)
> 
> Yes then this is a dup of that bug then.  The problem is that the middle-end
> did not know what the target was doing so it rejected sib calling in this case.
> 

Any idea why the patch for bug 23150 doesn't fix 4.0.2 ??
(the patch applies OK without any manual editing).

What is the procedure for getting fixes in 3.4.x and 4.0.x ??
Or should users just wait until 4.1 is released ??


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24675


  parent reply	other threads:[~2005-11-10  1:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 15:05 [Bug c/24675] New: " bill dot thompsons at gmail dot com
2005-11-04 15:08 ` [Bug target/24675] " pinskia at gcc dot gnu dot org
2005-11-09  2:11 ` armcc2000 at yahoo dot com
2005-11-09  4:21 ` armcc2000 at yahoo dot com
2005-11-09  4:31 ` pinskia at gcc dot gnu dot org
2005-11-09  6:21 ` armcc2000 at yahoo dot com
2005-11-09 22:04 ` mikpe at csd dot uu dot se
2005-11-09 23:33 ` armcc2000 at yahoo dot com
2005-11-09 23:41 ` pinskia at gcc dot gnu dot org
2005-11-10  1:25 ` armcc2000 at yahoo dot com [this message]
2005-11-11  0:56 ` bill dot thompsons at gmail dot com

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=20051110012508.6717.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).