public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001111] Access to saved registers from Cortex-M ISR
Date: Mon, 10 Jan 2011 14:28:00 -0000	[thread overview]
Message-ID: <20110110142754.2A5472F7800C@mail.ecoscentric.com> (raw)
In-Reply-To: <bug-1001111-13@http.bugs.ecos.sourceware.org/>

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.


  parent reply	other threads:[~2011-01-10 14:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-07 11:29 [Bug 1001111] New: " bugzilla-daemon
2011-01-07 13:39 ` [Bug 1001111] " bugzilla-daemon
2011-01-07 14:36 ` bugzilla-daemon
2011-01-10 12:11 ` bugzilla-daemon
2011-01-10 14:28 ` bugzilla-daemon [this message]
2011-01-10 14:28 ` bugzilla-daemon
2011-01-13 11:47 ` bugzilla-daemon
2011-01-13 17:36 ` bugzilla-daemon
2011-01-13 18:01 ` bugzilla-daemon
2011-01-13 18:42 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2011-01-07 11:29 [Bug 1001111] New: " bugzilla-daemon
2011-01-07 13:39 ` [Bug 1001111] " bugzilla-daemon
2011-01-07 14:36 ` bugzilla-daemon
2011-01-10 12:11 ` bugzilla-daemon
2011-01-10 14:28 ` bugzilla-daemon
2011-01-10 14:28 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110110142754.2A5472F7800C@mail.ecoscentric.com \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).