Assembly code errors

[Dave Ashley]

When I write some assembly code and I've got the syntax wrong, the build
fails but the line numbers reported in error messages don't relate to the
source I'm working on. I'm wondering could the build process for the assembly
code be changed so the python script creates a global
  toplevel.asm
file that has within it #includes for all the source files? So rather than
cat'ing all the files, you let the compiler include them, so its error
messages will be informative.

There's nothing especially bad about ASM code development, but things
like accurate error reporting can make it easier (or harder when absent).

-Dave

Dave Ashley <[e-mail]> writes:
> When I write some assembly code and I've got the syntax wrong, the build
> fails but the line numbers reported in error messages don't relate to the
> source I'm working on. I'm wondering could the build process for the assembly
> code be changed so the python script creates a global
>   toplevel.asm
> file that has within it #includes for all the source files? So rather than
> cat'ing all the files, you let the compiler include them, so its error
> messages will be informative.

So far it is CPP doing the including.   You can look at the crt0.s file
and track down the error from there.  Imperfect but it works.

The long term solution is to use romcc.  That already reports the correct
line numbers.
> There's nothing especially bad about ASM code development, but things
> like accurate error reporting can make it easier (or harder when absent).

I agree it is nice not to need an intermediate step.  Unless it is an absolutely
trivial change we probably won't do anything for the freebios1 tree.  As we don't want
to break anything.

Eric

[ron minnich]

On 18 Jul 2003, Eric W. Biederman wrote:
> > There's nothing especially bad about ASM code development, but things
> > like accurate error reporting can make it easier (or harder when absent).
>
> I agree it is nice not to need an intermediate step.  Unless it is an absolutely
> trivial change we probably won't do anything for the freebios1 tree.  As we don't want
> to break anything.

yes, I'm sorry about this, but we're trying hard to freeze the 1 tree. 
This is a big change and I think it is too late for it.

ron

Assembly code errors [PMX:#]

[Greg Watson]

This is what the new configuration scheme in freebios2 does.

Greg

At 2:25 PM -0700 18/7/03, Dave Ashley wrote:
> When I write some assembly code and I've got the syntax wrong, the build
> fails but the line numbers reported in error messages don't relate to the
> source I'm working on. I'm wondering could the build process for the assembly
> code be changed so the python script creates a global
>   toplevel.asm
> file that has within it #includes for all the source files? So rather than
> cat'ing all the files, you let the compiler include them, so its error
> messages will be informative.
>
> There's nothing especially bad about ASM code development, but things
> like accurate error reporting can make it easier (or harder when absent).
>
> -Dave
> _______________________________________________
> Linuxbios mailing list
> [e-mail]
> http://www.clustermatic.org/mailman/listinfo/linuxbios