linux-assembly.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randall Hyde" <aoax86@earthlink.net>
To: Corey Holcomb-Hockin <crsntlvs@ipeg.com>, linux-assembly@vger.kernel.org
Subject: Re: C structures and gas
Date: Mon, 11 Nov 2002 21:56:52 -0800	[thread overview]
Message-ID: <002a01c28a10$4c418f70$6701a8c0@rhyde> (raw)
In-Reply-To: 3DD04E99.5080704@ipeg.com

Well, the best way to do it in Gas is to use HLA and have
HLA generate the Gas code for you :-)
Seriously, though, Gas doesn't have much in the way of
abstract data typing capabilities.  If you want to move
beyond the minimal features available in Gas or NASM,
you're a prime candidate to learn assembly under HLA
(the High Level Assembler).  Not only does HLA support
records (structures), unions, and classes, but it provides
some very flexible options for controlling the alignment of
objects within the structures so that your assembly structs
can be made compatible with just about any compiler
out there (C or otherwise).
You can check out HLA at http://webster.cs.ucr.edu
Randy Hyde
----- Original Message ----- 
From: "Corey Holcomb-Hockin" <crsntlvs@ipeg.com>
To: <linux-assembly@vger.kernel.org>
Sent: Monday, November 11, 2002 4:43 PM
Subject: C structures and gas


> What is the best way to access C structures with gas assembly?  I 
> haven't gotten any good ideas from looking at assembly generated from C 
> code.  It looks like it keeps track of offsets and the size of 
> structures on its own.  I would have a hard time keeping track of 
> offsets and changing them if the structure changed.
> 
> Corey Holcomb-Hockin
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-assembly" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2002-11-12  5:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12  0:43 C structures and gas Corey Holcomb-Hockin
2002-11-12  2:51 ` Scott Lanning
2002-11-12  5:56 ` Randall Hyde [this message]
2002-11-28  6:15 ` Christian Hildner

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='002a01c28a10$4c418f70$6701a8c0@rhyde' \
    --to=aoax86@earthlink.net \
    --cc=crsntlvs@ipeg.com \
    --cc=linux-assembly@vger.kernel.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 NNTP newsgroup(s).