bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug ld/21472] [avr] Add new emulation for ATtiny416 et al.


From: mehmetgelisin at aol dot com
Subject: [Bug ld/21472] [avr] Add new emulation for ATtiny416 et al.
Date: Fri, 10 Sep 2021 19:36:32 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=21472

Mehmet gelisin <mehmetgelisin at aol dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mehmetgelisin at aol dot com

--- Comment #6 from Mehmet gelisin <mehmetgelisin at aol dot com> ---
open for > 12 years now and has been suspended.
 https://komiya-dental.com/ 
A comined GCC + GAS approach would be feasible, and this PR is the GAS part:

GAS implements a __gcc_isr pseudo-instruction which scans the code and emits
parts of ISR prologue and epilogue.

__gcc_isr 1: GAS will replace it by an ISR prologue chunk (at most 6 insns).

__gcc_isr 2: GAS will replace it by an ISR epilogue chunk (at most 5 insns).
 http://www.iu-bloomington.com/ 
__gcc_isr 0, Rx:  Scan the code since the last prologue chunk and replace all
encountered prologue and epilogue chunks by appropriate code. Rx is general
purpose register.
 https://www.webb-dev.co.uk/ 
During parse (md_assemble), prologue and epilogue chunks are represented as
rs_machine_dependent fragments.  If "__gcc_isr 0, Rx" is seen, all
rs_machine_dependent fragments in the current chain are transformed into
ordinary rs_fill code fragments of then known fixed size.

After parse (md_pre_output_hook) a sanity check is performed which reports any
dangling chunks.
https://waytowhatsnext.com/  
__gcc_isr is only available with the new command line option

open for > 12 years now and has been suspended.

A comined GCC + GAS approach would be feasible, and this PR is the GAS part:

GAS implements a __gcc_isr pseudo-instruction which scans the code and emits
parts of ISR prologue and epilogue.
http://www.acpirateradio.co.uk/ 
__gcc_isr 1: GAS will replace it by an ISR prologue chunk (at most 6 insns).

__gcc_isr 2: GAS will replace it by an ISR epilogue chunk (at most 5 insns).

__gcc_isr 0, Rx:  Scan the code since the last prologue chunk and replace all
encountered prologue and epilogue chunks by appropriate code. Rx is general
purpose register.
http://www.logoarts.co.uk/ 
During parse (md_assemble), prologue and epilogue chunks are represented as
rs_machine_dependent fragments.  If "__gcc_isr 0, Rx" is seen, all
rs_machine_dependent fragments in the current chain are transformed into
ordinary rs_fill code fragments of then known fixed size.
 http://www.slipstone.co.uk/ 
After parse (md_pre_output_hook) a sanity check is performed which reports any
dangling chunks.

__gcc_isr is only available with the new command line option

open for > 12 years now and has been suspended. http://embermanchester.uk/ 

A comined GCC + GAS approach would be feasible, and this PR is the GAS part:

GAS implements a http://connstr.net/  __gcc_isr pseudo-instruction which scans
the code and emits parts of ISR prologue and epilogue.

__gcc_isr 1: GAS will http://joerg.li/ replace it by an ISR prologue chunk (at
most 6 insns).

__gcc_isr 2: GAS will replace it by an ISR epilogue chunk (at most 5 insns).
 http://www.jopspeech.com/
__gcc_isr 0, Rx:  Scan the code since the last prologue chunk and replace all
encountered prologue and epilogue chunks by appropriate code. Rx is general
purpose register. http://www.wearelondonmade.com/

During parse (md_assemble), prologue and epilogue chunks are represented as
rs_machine_dependent fragments.  If "__gcc_isr 0, Rx" is seen, all rs_machine
http://www.compilatori.com/ _dependent fragments in the current chain are
transformed into ordinary rs_fill code fragments of then known fixed size.

After parse (md_pre_output_hook) a sanity check is performed which reports any
dangling chunks. http://www-look-4.com/

__gcc_isr is only available with the new command line option

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]