[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130730150308.GA18483@openwall.com>
Date: Tue, 30 Jul 2013 19:03:08 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: Daniel's weekly report #7
Daniel,
On Tue, Jul 30, 2013 at 09:50:16AM +0200, D?niel Bali wrote:
> On Jul 30, 2013 3:53 AM, "Solar Designer" <solar@...nwall.com> wrote:
> > Here's the corresponding commit:
> >
> https://github.com/balidani/gcnasm/commit/9adcd876b389d4296f2f217577bd95906142478a
> >
> > Do we really need this? I think that for any serious use we'd be
> > passing our source code through cpp, which includes more complete macro
> > support. I don't mind having this functionality in, though.
>
> By passing source code through cpp do you mean the GCN ISA source?
Yes.
> So we would be doing some sort of static analysis and optimize that way?
No. Please take a look at e.g. x86.S (note the uppercase "S", which
means that cpp is enabled) to see how we use cpp macros when programming
in assembly. I think we'll approach GCN ISA asm in a similar fashion.
> This will only be useful when writing GCN ISA code by hand.
Isn't this exactly what we're going to be doing?
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
