This is the mail archive of the ecos-bugs@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug 1001111] Access to saved registers from Cortex-M ISR


Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001111

John Dallaway <john@dallaway.org.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned@bugs.ecos.source |john@dallaway.org.uk
                   |ware.org                    |
         AssignedTo|unassigned@bugs.ecos.source |john@dallaway.org.uk
                   |ware.org                    |

--- Comment #4 from John Dallaway <john@dallaway.org.uk> 2011-01-10 14:27:50 GMT ---
(In reply to comment #3)
> (In reply to comment #2)
> 
> > I looked at hal_saved_interrupt_state, but it is declared only when the GDB
> > break/Ctrl-C support is enabled. So...
> 
> One approach would be for any interested code to define its own instance of
> hal_saved_interrupt_state if the break/ctrl-c code is not included. There are
> precedents for this. However...

Each package which contains such interested code would then need to be aware of
every other package which also contains interested code and there would need to
be some priority mechanism to determine which package defines the symbol.

> > I would like to propose a CYGINT_HAL_COMMON_SAVED_INTERRUPT_STATE_REQUIRED CDL
> > interface which controls the declaration of 'hal_saved_interrupt_state'.
> 
> This seems a perfectly sensible solution.

OK. I'll develop a patch along these lines. Thanks, again, for your input.

--- Comment #5 from John Dallaway <john@dallaway.org.uk> 2011-01-10 14:27:50 GMT ---
(In reply to comment #3)
> (In reply to comment #2)
> 
> > I looked at hal_saved_interrupt_state, but it is declared only when the GDB
> > break/Ctrl-C support is enabled. So...
> 
> One approach would be for any interested code to define its own instance of
> hal_saved_interrupt_state if the break/ctrl-c code is not included. There are
> precedents for this. However...

Each package which contains such interested code would then need to be aware of
every other package which also contains interested code and there would need to
be some priority mechanism to determine which package defines the symbol.

> > I would like to propose a CYGINT_HAL_COMMON_SAVED_INTERRUPT_STATE_REQUIRED CDL
> > interface which controls the declaration of 'hal_saved_interrupt_state'.
> 
> This seems a perfectly sensible solution.

OK. I'll develop a patch along these lines. Thanks, again, for your input.

-- 
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]