From: "Kris Warkentin" <kewarken@qnx.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <Richard.Earnshaw@arm.com>, <gdb-patches@sources.redhat.com>
Subject: Re: [rfa?] Add frame_align(); Was: ARM stack alignment on hand called functions
Date: Wed, 29 Jan 2003 14:50:00 -0000 [thread overview]
Message-ID: <13c601c2c7a5$a0170670$0202040a@catdog> (raw)
In-Reply-To: <3E372191.2050609@redhat.com>
Seems to be okay on this end.
Kris
----- Original Message -----
From: "Andrew Cagney" <ac131313@redhat.com>
To: "Andrew Cagney" <ac131313@redhat.com>
Cc: <Richard.Earnshaw@arm.com>; "Kris Warkentin" <kewarken@qnx.com>;
<gdb-patches@sources.redhat.com>
Sent: Tuesday, January 28, 2003 7:34 PM
Subject: Re: [rfa?] Add frame_align(); Was: ARM stack alignment on hand
called functions
> >>> >> +/* Ensure that the ARM's stack pointer has the correct alignment
for a
> >>> >> + new frame. */
> >>> >> +static CORE_ADDR
> >>> >> +arm_frame_align (struct gdbarch *gdbarch, CORE_ADDR addr)
> >>> >> +{
> >>> >> + return (addr & -16);
> >>> >> +}
> >
> > You mean ~(ULONGEST)0x7?
> >
> > I mean ~(typeof(addr)) 0x7.
> >
> > M'kay (finally gets brain around what that expression is doing), back to
the patch.
> >
> > Does it fix the bug?
>
> Anyone?
>
> Andrew
>
>
>
prev parent reply other threads:[~2003-01-29 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200211270917.gAR9HNE29771@pc960.cambridge.arm.com>
2002-11-27 10:43 ` Andrew Cagney
2002-11-28 1:26 ` Richard Earnshaw
2002-11-28 2:20 ` Andreas Schwab
2002-11-28 2:41 ` Richard Earnshaw
2002-11-28 2:45 ` Andreas Schwab
2002-11-28 2:57 ` Richard Earnshaw
2002-11-28 5:52 ` Keith Walker
2002-11-28 7:34 ` Andrew Cagney
2002-11-28 7:19 ` Andrew Cagney
2002-11-28 8:33 ` Richard Earnshaw
2002-11-28 8:45 ` Andrew Cagney
2002-11-28 8:50 ` Richard Earnshaw
2002-11-28 9:00 ` Andrew Cagney
2003-01-29 5:19 ` Andrew Cagney
2003-01-29 14:50 ` Kris Warkentin [this message]
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='13c601c2c7a5$a0170670$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=Richard.Earnshaw@arm.com \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/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