public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org>
To: "SRUTHY C.N." <csy2p100@nitc.ac.in>
Cc: gcc@gcc.gnu.org
Subject: Re: RTL
Date: Thu, 28 Aug 2003 00:47:00 -0000	[thread overview]
Message-ID: <3F4D2B51.8070508@tuliptree.org> (raw)
In-Reply-To: <2167.210.212.228.79.1061982697.webmail@ebox.nitc.ac.in>

SRUTHY C.N. wrote:
>  why this alignment to multiple of 16?

This is an incomplete bug report.  It is important to give testcases, 
compiler options, compiler versions, etc.

It is probably an accident of implementation.  You can use __alignof() 
to get the structure alignment, and see that it is only 4.  However, we 
need to align the stack in the function main to 16-bytes because 16-byte 
alignment gives better code, and not all systems have startup code that 
give a 16-byte aligned stack.  So if your testcase defines the structure 
in main, it might appear to have 16-byte alignment but it really 
doesn't.  Define the structure in a function with any other name, and 
you will see differently.  This probably would have been obvious if you 
had bothered to include a testcase.

>   Is RTL representation  dependent on GCC version? 

The format changes infrequently.  The contents change frequently, since 
they depend on gcc features and optimizations which change all of the time.

gcc-2.96 to gcc-3.2 is really a very long time in terms of gcc 
development, because of how rapidly gcc changes.  You can't expect 
things to be the same between those two versions.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

  parent reply	other threads:[~2003-08-27 22:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-27 17:47 RTL SRUTHY C.N.
2003-08-27 18:08 ` RTL SRUTHY C.N.
2003-08-28  0:47 ` Jim Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-25  4:37 RTL Sruthy C.N
2003-09-25  4:38 ` RTL Sruthy C.N
2003-09-25  5:02 ` RTL Jim Wilson
2003-09-30 12:45   ` RTL Sruthy C.N
2003-10-06 23:27     ` RTL Jim Wilson
2003-09-30 13:12   ` RTL Sruthy C.N
2003-08-29 14:24 RTL SRUTHY C.N.
2003-08-29 14:41 ` RTL SRUTHY C.N.
2002-10-04  1:36 rtl N V Krishna
2002-10-04  7:07 ` rtl Shekhar Divekar
2002-10-04 12:00 ` rtl Mike Stump

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=3F4D2B51.8070508@tuliptree.org \
    --to=wilson@tuliptree.org \
    --cc=csy2p100@nitc.ac.in \
    --cc=gcc@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).