From: Freddie Chopin <freddie_chopin@op.pl>
To: newlib@sourceware.org
Subject: Re: [PATCH, newlib] Allow locking routine to be retargeted
Date: Wed, 14 Dec 2016 15:27:00 -0000 [thread overview]
Message-ID: <1481729199.1284.1.camel@op.pl> (raw)
In-Reply-To: <800fa569-cd83-bd61-95e3-7ad83e053d6c@foss.arm.com>
On Wed, 2016-12-14 at 14:36 +0000, Thomas Preudhomme wrote:
> Why is struct _lock easier to debug by the way?
I think the reason is that in user code - which does the "retargeting"
- _lock can be defined to be whatever is needed, so in the debugger you
see the contents of the struct. If you use void*, then you have to do
manual casting in debugger to see these contents.
I think this will also help to keep the retargeting code valid - now
the compiler can check whether you use correct types - either _lock or
it's address, while with void* the compiler will happily accept almost
anything.
Regards,
FCh
next prev parent reply other threads:[~2016-12-14 15:27 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 17:18 Thomas Preudhomme
2016-12-13 20:13 ` Freddie Chopin
2016-12-14 11:54 ` Thomas Preudhomme
2016-12-14 12:39 ` Freddie Chopin
2017-01-11 13:09 ` Thomas Preudhomme
2016-12-13 21:11 ` Freddie Chopin
2016-12-13 21:41 ` Freddie Chopin
2016-12-14 14:22 ` Sebastian Huber
2016-12-14 14:36 ` Thomas Preudhomme
2016-12-14 14:52 ` Thomas Preudhomme
2017-01-09 18:49 ` Freddie Chopin
2017-01-10 16:50 ` Thomas Preudhomme
2017-01-10 17:07 ` Freddie Chopin
2017-01-11 16:09 ` Thomas Preudhomme
2017-01-11 16:46 ` Craig Howland
2017-01-11 17:48 ` Thomas Preudhomme
2017-01-11 18:08 ` Craig Howland
2017-01-11 19:14 ` Freddie Chopin
2017-01-12 10:52 ` Thomas Preudhomme
2017-01-12 16:20 ` Freddie Chopin
2017-01-12 16:55 ` Thomas Preudhomme
2017-01-13 11:25 ` Thomas Preudhomme
2017-01-13 13:24 ` Thomas Preudhomme
2017-01-13 18:05 ` Freddie Chopin
2017-01-13 18:16 ` Thomas Preudhomme
2017-01-16 15:59 ` Thomas Preudhomme
2017-01-20 13:37 ` Thomas Preudhomme
2017-01-20 13:55 ` Freddie Chopin
2017-01-24 10:00 ` Freddie Chopin
2017-01-25 12:31 ` Corinna Vinschen
2017-01-30 10:51 ` Thomas Preudhomme
2016-12-14 15:27 ` Freddie Chopin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-10 14:42 Thomas Preudhomme
2016-11-10 15:34 ` Freddie Chopin
2016-11-10 16:05 ` Thomas Preudhomme
2016-11-10 20:32 ` Freddie Chopin
2016-11-10 20:35 ` Freddie Chopin
2016-11-11 11:09 ` Thomas Preudhomme
2016-11-11 11:54 ` Freddie Chopin
2016-11-11 11:56 ` Sebastian Huber
2016-11-11 13:40 ` Thomas Preudhomme
2016-11-11 14:10 ` Freddie Chopin
2016-11-23 14:38 ` Thomas Preudhomme
2016-11-23 15:52 ` Freddie Chopin
2016-11-24 7:44 ` Sebastian Huber
2016-11-24 8:29 ` Freddie Chopin
2016-11-25 10:21 ` Thomas Preudhomme
2016-11-25 12:04 ` Thomas Preudhomme
2016-11-25 12:35 ` Sebastian Huber
2016-12-13 17:20 ` Thomas Preudhomme
2016-11-25 14:12 ` Freddie Chopin
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=1481729199.1284.1.camel@op.pl \
--to=freddie_chopin@op.pl \
--cc=newlib@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).