public inbox for
 help / color / mirror / Atom feed
From: Ian Lance Taylor <>
Subject: Re: Maximum Alignment Restrictions
Date: Thu, 11 Jan 1996 11:22:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.SV4.3.91.960111113044.4093B-100000@merlin>

   Date: Thu, 11 Jan 1996 11:32:55 -0600 (CST)
   From: Joel Sherrill <>

   What is the rationale for the maximum alignment supported on a particular 
   CPU family?  

There is no such maximum in BFD.  In BFD, a CPU type provides a
default alignment.

   My current problem is that the SPARC trap table must be on a 4K boundary
   but that appears to be too large. 

   My thinking is that there is no particular reason (except object format 
   limitations) to place a CPU dependent limit on maximum alignment boundary.

There is no other reason.

In what way is this affecting you?  You didn't say what target you are
using.  Perhaps you are using a SPARC a.out target.  The problem there
is the a.out object file format has no way to specify the alignment of
a section.  BFD must guess, and it guesses based on the CPU type.  The
CPU type is not specifying a maximum alignment.  It is providing a
default alignment to use when the alignment can not be otherwise


  reply	other threads:[~1996-01-11 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-11  9:41 Joel Sherrill
1996-01-11 11:22 ` Ian Lance Taylor [this message]
1996-01-11 11:37 ` David S. Miller

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).