compiling assembly.s files in gcc ... was: gcc wont compile with // comments?

[Karlos]

Hmm, thats the one I already got. IIRC the installer skipped gcc saying it wasnt included for size reasons...Better have a closer look at it :lol:

-edit-

Just did - the one I had was 14Mb compressed so not the same at all :-)

[cycloid]

i'm getting closer. by examining other peoples source i can now properly declare/prototype functions that would, otherwise, use __asm. here it is

#ifdef __SASC
#   define SAVEDS       __saveds
#   define ASM          __asm
#   define REG(x,y)     register __##x y
#elif defined(__GNUC__)
#   define SAVEDS       __saveds
#   define ASM
#   define REG(x,y)     y __asm(#x)
#elif defined(_DCC)
#   define SAVEDS       __geta4
#   define ASM
#   define REG(x,y)     __##x y
#elif defined(__STORM__)
#   define SAVEDS       __saveds
#   define ASM
#   define REG(x,y)     register __##x y
#elif defined(__VBCC__)
#   define SAVEDS       __saveds
#   define ASM
#   define REG(x,y)     __reg(#x) y
#else
#   error   add #defines for your compiler...
#endif

if anyone understands, that is, i found it in the blitzquake source: amigacompiler.h, heh.

then you can proto your function thus:

static void ASM thefunction( REG(a1,UBYTE *), REG(a2,UBYTE *), REG(a6,struct Library *));



NEXT PROBLEM:

compiling assembler ("whatever.s") files in gcc (as) ... i get an error for EVERY line of assembler along the lines of:

 unknown operator -- statement: ASM STATEMENT

or

parse error -- ASM STATEMENT

and

rest of line ignored, first ignored character is '@'



anyone?

[Steady]

If you have a pure assembler file, you need to use an assembler to compile separate object code to be linked later on. The gcc compiler is expecting C syntax, which is why the asm() stuff is needed in the C program.

Maybe gcc has an assembler option that will do the trick. I don't know and can't check because I ain't got it. Someone else should help with that.

[cycloid]

i knew somebody would say that.. gcc auto detects assembly files (extension *.s is the standard) and passes them over to it's own assembly compiler, "as". i've got "phxass" too but i cant get make to let me use it for some reason, bizzare.

NEXT!

[Steady]

Which is why I said that there might be an option. Only offering up possibilities.

[cycloid]

yer, well it starts off with something like "Assembler Output:" before giving me all the errors. i'm half way now to figuring phxass out now. though i suspect i need to use it for the intermidiate assempler->object for the gcc c compiled files also. though i wouldnt know how to do that either!

[ncafferkey]

I think the assembler format accepted by as is a bit different from that accepted by PhxAss. Also, the GNU linker needs a.out format object files as input, whereas PhxAss generates Amiga-native hunk format files. I don't know if there's any solution to this problem. Not accepting hunk files has been one of the main problems with Amiga GCC for a long time.

If you still have problems with comments, apparently gcc accepts C++ comments as long as -ansi or -traditional aren't used.

[cycloid]

well, i havent got as far as the hunk stage, as i'm still stuck at the assembly.s file stage. i first thought it might have been a pedantic syntax error. e.g. not having the commands at the first tab, or having lower case instructions instead of uppercase. but that's about my limit of assembly knowledge! really.

my // comments are accepted by gcc330, which is what i'm using now

[cycloid]

again, i'm lurching along one inch at a time. if i manually instruct phxass to compile a filename.s file then it's happy to do so. howevery i get a bunch of errors relating to FUNCDEF. from what i can gather i need a funcdef macro, well there's one in libraries.i thus

   FUNCDEF       MACRO
   _LVO\1       EQU   FUNC_CNT
   FUNC_CNT    SET   FUNC_CNT-6
   FUNC_CNT    EQU   LIB_USERDEF   
          ENDM

which doesnt do the job, phxass simply says "unkown directive" for each line.

my other problem is somehow getting phxass and gcc's make to coexist so i dont have to manually do each .s file. and i still don't know if there will be issues with phxass's outputs and gccs.

[NovaCoder]

To continue this old thread....

I'm having the same kind of issues as this guy was. In theory you should just be able to add assembler sources directly to a project in StormC V4 when using the gcc compiler but that doesn't work for me (or him).

So now I'm using PhxAss to compile the assembly files to object files and adding them to my StormC project. I then have to use a special header file declaration as follows:


Code:
#define REG(reg,arg) arg __asm(#reg)
 
void setVol (REG(d0, int vol));

This works great as long as the project is in plain C but if I want to create a C++ project I get linker errors (adding extern to function definition doesn't help).

Anyone got any ideas?

[x303]

#define REG(reg,arg) arg __asm(#reg)

I'm not sure if stormgcc (especially c++) like the __asm bit. It might work if you remove it.

x303

[NovaCoder]

Nope, that gives a syntax error

[NovaCoder]

Update:  Seems to work with a 'simple' prototype

eg void setVol(int vol);

[asymetrix]

Here are some links to help with installing GCC on Amiga :


http://amidevcpp.amiga-world.de/index.php?HR_LANG=english


http://code.google.com/p/guidetoamigacompatibleprogramming/source/browse/trunk/english/CAP_2.txt

Developer Winuae hardfile, working gcc, assembler
http://www.innoidea.hu/subsites/amiga/developer/FILES/HardFiles/gcc111.zip

Real amiga
http://www.innoidea.hu/subsites/amiga/developer/FILES/HardFiles/gcc111-files.tgz

Cross compile using VS
http://utilitybase.com/article/show/2008/05/12/240/Cross+Compiling+for+OS4+or+OS3+using+MS+Visual+Studio+2005

OS4 cross compile
http://utilitybase.com/article/show/2007/06/23/231/Installing+an+AmigaOS+4+cross+compiler

[unusedunused]

is that right?

it's c code (adoom)

it says "parse error before /" on line 1 of every file.

yes i know // is c++ but it's also c99

If you want that the gcc assembler gas support C style defines and includes, you need name in makefile the filename extension a capital s.

so assembly.S should support in C comment syntax.

[Karlos]

To continue this old thread....

(snip)

Anyone got any ideas?

I got around all my C++ / asm combination problems by using inline C++ functions that call asm() construct directly.

For example

Code: [Select]


  inline uint32 swap32(uint32 val)
  {
    if (__builtin_constant_p(val)) {
      val = val<<16 | val>>16;
      val = ((val&0x00FF00FF)<<8) | ((val&0xFF00FF00)>>8);
    } else {
      asm(
        &quot;rol.w #8, %0\n\t&quot;
        &quot;swap %0\n\t&quot;
        &quot;rol.w #8, %0&quot;
        : &quot;=d&quot;(val)
        : &quot;0&quot;(val)
        : &quot;cc&quot;
      );
    }
    return val;
  }

You can (and I have) used the asm() statement inside an inline C++ function to jsr to an externally referenced function written in assembler. Just make sure the variables passed to your inline function are loaded into the correct registers inside the asm() just before you jsr and add those registers to the clobber list so the compiler knows your call is going to trash them.