public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Kris Warkentin" <kewarken@qnx.com>,
	"Daniel Jacobowitz" <drow@mvista.com>
Cc: <gdb@sources.redhat.com>
Subject: Re: long long considered harmful?
Date: Tue, 22 Apr 2003 19:25:00 -0000	[thread overview]
Message-ID: <081f01c30904$ea5b7f90$0202040a@catdog> (raw)
In-Reply-To: <080801c30903$2dc0ae60$0202040a@catdog>

> > > typedef struct mips_cpu_registers
> > > {
> > >   unsigned regs[74];
> > >   unsigned long long regs_alignment;
> > > } MIPS_CPU_REGISTERS;
> >
> > What's the purpose of the alignment entry?  I doubt it does what you
> > want it to.
>
> I was more or less correct on this one.  Apparently this was not even
> defined by us but by one of our very large chip vendors who shall remain
> nameless.  Rather than the nicer solution of just defining an array of 64
> bit regs, they did this which necessitates some nastiness when dealing
with
> different endians.  The alignment field ensures that the overall structure
> is 64 bit aligned which is a handy thing to be on mips.

Pardon me, by overall structure, I mean the starting address of the
structure.  Having a 64 bit entry causes the compiler to align the structure
on a 64 bit boundary.

cheers,

Kris

  reply	other threads:[~2003-04-22 19:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 17:39 Kris Warkentin
2003-04-22 17:45 ` Daniel Jacobowitz
2003-04-22 18:08   ` Kris Warkentin
2003-04-22 18:21     ` Daniel Jacobowitz
2003-04-22 18:41       ` Kris Warkentin
2003-04-22 19:31         ` Daniel Jacobowitz
2003-04-22 19:12   ` Kris Warkentin
2003-04-22 19:25     ` Kris Warkentin [this message]
2003-04-22 19:30       ` Daniel Jacobowitz
2003-04-23 13:39         ` Kris Warkentin
2003-04-23 21:17           ` Daniel Jacobowitz
2003-04-23 21:23             ` Kris Warkentin
2003-04-23 21:44               ` Kris Warkentin
2003-04-23 21:47                 ` Daniel Jacobowitz
2003-04-23 22:09                   ` Kris Warkentin
2003-04-23 22:11                     ` Daniel Jacobowitz
2003-04-23 22:17                       ` Kris Warkentin
2003-04-24 21:05               ` Andrew Cagney
2003-04-24 23:51                 ` Kris Warkentin

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='081f01c30904$ea5b7f90$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=drow@mvista.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).