From: Stefan Ring <stefanrin@gmail.com>
To: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Wrong assembly code generated from C code (ARM Cortex-m3) ?
Date: Thu, 2 Dec 2021 20:26:08 +0100 [thread overview]
Message-ID: <CAAxjCEzaBZ398Z9eTjv2RoWiiiigBsYRDKJgBM-YPZ1k8h-WoQ@mail.gmail.com> (raw)
In-Reply-To: <87lf13geou.fsf@k-7.ch>
On Thu, Dec 2, 2021 at 5:22 PM Sébastien Gendre <seb@k-7.ch> wrote:
>
> And I'm sure I can run code on the microcontroller because if I don't
> declare the pointers to the registers and I just declare an int variable
> and set its values multiple times it work (I can run it, inspect
> variables, place breakpoints, etc). For debug I use GDB.
I would at least not use Thumb in the beginning. This is notoriously
annoying to debug in gdb because you can never be sure that the CPU's
and the debugger's opinion on the current operating mode agree.
next prev parent reply other threads:[~2021-12-02 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 12:38 Sébastien Gendre
2021-12-02 15:44 ` David Brown
2021-12-02 16:06 ` Sébastien Gendre
2021-12-02 19:26 ` Stefan Ring [this message]
2021-12-02 19:35 ` Stefan Ring
2021-12-02 21:58 ` David Brown
2021-12-08 5:51 ` Sébastien Gendre
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=CAAxjCEzaBZ398Z9eTjv2RoWiiiigBsYRDKJgBM-YPZ1k8h-WoQ@mail.gmail.com \
--to=stefanrin@gmail.com \
--cc=gcc-help@gcc.gnu.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).