public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.co.uk>
To: Gary Thomas <gthomas@redhat.com>
Cc: Chris Morrow <cmorrow@YottaYotta.com>,
	ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] 64 bit mips arch, and __DEVTAB__
Date: Wed, 12 Jul 2000 16:50:00 -0000	[thread overview]
Message-ID: <396D0457.CD53B198@redhat.co.uk> (raw)
In-Reply-To: <XFMail.20000712162425.gthomas@redhat.com>

Gary Thomas wrote:
> 
> On 12-Jul-2000 Chris Morrow wrote:
> > I'm working on porting eCos to a 64 bit mips cpu and have encountered
> > a problem with the DEVTAB_ENTRY macro defined in
> > io/common/current/include/devtab.h. It would appear that gcc is aligning
> > each piece of data added to the .devtab section on 8 byte boundries.
[snip]

OOI I thought it would be interesting to see what gcc does here, with the
constructor lists. In config/mips/elf64.h it has:

#define ASM_OUTPUT_CONSTRUCTOR(FILE,NAME)                             \
  do {                                                                \
    ctors_section ();                                                 \
    fprintf (FILE, "\t%s\t", (Pmode == SImode) ? ".word" : ".dword"); \
    assemble_name (FILE, NAME);                                       \
    fprintf (FILE, "\n");                                             \
  } while (0)

So it explicitly uses assembler. It might be interesting to look at bug.s
(generated by compiling with --save-temps ) and check that it is gcc adding
the alignments itself, and not the assembler. Perhaps Chris can send the
appropriate extract, since it will only take him a second.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  parent reply	other threads:[~2000-07-12 16:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-12 15:15 Chris Morrow
2000-07-12 15:24 ` Gary Thomas
2000-07-12 15:52   ` Chris Morrow
2000-07-12 16:50   ` Jonathan Larmour [this message]
2000-07-12 17:00     ` Chris Morrow

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=396D0457.CD53B198@redhat.co.uk \
    --to=jlarmour@redhat.co.uk \
    --cc=cmorrow@YottaYotta.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@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).