4

Currently, I'm learning GNU as, and find a lot useful information in "info as".

I found ".set noat" is used in MIPS specified code, but when searching for this directive in "info as", I found its explanation in node "alpha directive", but not in "MIPS Dependent Features". Why? did I miss something in the manual?

TIA

plaes
  • 31,788
  • 11
  • 91
  • 89
Wangrui
  • 167
  • 2
  • 11

2 Answers2

2

The .set at/noat is a valid construction for MIPS architecture and works the similar way as on Alpha by disabling/enabling warning when $at register is used by user.

As sometimes happens, documentation and code are not always 100% in sync. So please file a bug against binutils and even better - provide a patch. By doing that, you can learn from the pros (unless they are really busy, like sometimes happens).

About MIPS vs Alpha: it seems that the Alpha architecture has been greatly influenced by MIPS's.

plaes
  • 31,788
  • 11
  • 91
  • 89
  • It is a bit of difficult to dip into gnu tool chain source code. I just want to find out whether or not ".set noat" mentioned in "alpha directive" workable for mips environment. Is there some easier way to cope with this problem? testing the ".set noat" in "alpha directive" in mips, no easier? – Wangrui Oct 27 '11 at 06:13
  • [src/gas/config/tc-mips.c:235](http://sourceware.org/cgi-bin/cvsweb.cgi/src/gas/config/tc-mips.c?annotate=1.493&cvsroot=src) – user786653 Oct 27 '11 at 06:17
  • 1
    Well, the bug report should be about missing documentation, as MIPS clearly support that directive. – plaes Oct 27 '11 at 07:02
2

GNU as supports gobs of processor targets (CPU architectures) from the 8041 micro-controller family to the mightiest Cray and beyond. The machine dependent section of the manual lists 42 architectures.

Most of the 121 pseudo instructions are common to all architectures, as well as the semantics of labels and references to them. The big differences between targets are the specific CPU instructions, address modes, and instruction encoding. Impressively, as can generate the same object file formats for most targets: COFF, ELF, a.out, and SOM.

Since most pseudo instructions affect the assembler, and not CPU execution, it is unsurprising that they would apply to a large number of architectures.

wallyk
  • 56,922
  • 16
  • 83
  • 148
  • another question for pros, where can i find documents for the cpu instructions in certain architecture? – Wangrui Oct 27 '11 at 07:04
  • @joey: usually at the manufacturer's website. A few (annoying) manufacturers try to charge for documentation, but most provide it free online. Many of the machine dependent sections of `as` have links to the manufacturer's documentation. – wallyk Oct 27 '11 at 07:16
  • could you give me a link? prefer to "-march=mips3". :) – Wangrui Oct 27 '11 at 07:23
  • @joey: Alas, the GNU `as` MIPS page says *See MIPS RISC Architecture, by Kane and Heindrich (Prentice-Hall)*. The manufacturer has a comprehensive list of documents at http://www.mips.com/products/product-materials/processor/mips-architecture/ . – wallyk Oct 27 '11 at 07:35