From: Simon Marchi <simon.marchi@polymtl.ca>
To: David Blaikie <dblaikie@gmail.com>
Cc: Tim Newsome <tim@sifive.com>, gdb <gdb@sourceware.org>
Subject: Re: Remote query for structure layout
Date: Tue, 30 Mar 2021 18:38:31 -0400 [thread overview]
Message-ID: <dcbbd140-314c-31ea-0510-f74ae07c0e0e@polymtl.ca> (raw)
In-Reply-To: <CAENS6Eu3DvsET82_x0kJ5u_uWucLPnyUk6eY+mdWLyGPByM32w@mail.gmail.com>
On 2021-03-30 6:03 p.m., David Blaikie wrote:>
> Perhaps - though I was thinking actually hardcoded in the compiler - since it's the one that chooses/knows the layout, it's not (presumably) using any code it reads from a header, etc, in user code to define the layout.
Is it really the compiler that decides this layout? My understanding is
that this is decided by the FreeRTOS code.
Having used FreeRTOS a few times, my understanding is that it's
basically a big library, the compiler doesn't really know about it. For
all it knows, you are compiling a bare metal program that happens to
implement a task system.
Simon
next prev parent reply other threads:[~2021-03-30 22:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.6.1616932808.1485743.gdb@sourceware.org>
2021-03-30 20:35 ` Tim Newsome
2021-03-30 21:33 ` Simon Marchi
2021-03-30 21:41 ` David Blaikie
2021-03-30 21:49 ` Simon Marchi
2021-03-30 22:03 ` David Blaikie
2021-03-30 22:38 ` Simon Marchi [this message]
2021-03-30 22:44 ` David Blaikie
2021-03-31 0:16 ` Simon Marchi
2021-03-31 3:27 ` David Blaikie
2021-03-31 13:00 ` Simon Marchi
2021-04-02 22:05 ` David Blaikie
2021-04-03 19:39 ` Simon Marchi
2021-03-31 14:06 ` Tim Newsome
2021-03-28 11:06 Thomas Weißschuh
2021-03-29 16:05 ` Simon Marchi
2021-03-29 17:33 ` Thomas Weißschuh
2021-03-29 19:42 ` Simon Marchi
2021-03-29 20:02 ` Philippe Waroquiers
2021-03-29 20:10 ` Simon Marchi
2021-03-29 20:20 ` Philippe Waroquiers
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=dcbbd140-314c-31ea-0510-f74ae07c0e0e@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=dblaikie@gmail.com \
--cc=gdb@sourceware.org \
--cc=tim@sifive.com \
/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).