Defined illegal instruction
Jan Beulich
jbeulich@suse.com
Mon Feb 12 07:29:14 GMT 2024
More information about the Binutils mailing list
Mon Feb 12 07:29:14 GMT 2024
- Previous message (by thread): Defined illegal instruction
- Next message (by thread): Defined illegal instruction
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10.02.2024 13:56, jacob navia wrote: > OK. So now we have: > > unimp and > c.unimp > > Both generate 16 bit zeroes if the C extension is present. > > If the C extension is not present, > unimp generates > > csrw cycle, x0 > > If we want to generate the defined unimplemented instruction in 32 bis we write > > .long 0 > > As in the power PC. Except that on RISC-V (and other architectures separating code from data by special labels, like Arm) you want to use .insn. Iirc this also ensures debug line info would be properly emitted, if enabled. Jan
- Previous message (by thread): Defined illegal instruction
- Next message (by thread): Defined illegal instruction
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list