From: R0b0t1 <r030t1@gmail.com>
To: Claudio Eterno <eterno.claudio@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Information on usage
Date: Fri, 08 Sep 2017 08:02:00 -0000 [thread overview]
Message-ID: <CAAD4mYiYujOYxiEJc91ii+-EJ0Cpgf81qC+EOwfYTQeTMvfWQg@mail.gmail.com> (raw)
In-Reply-To: <CA+moFQ_TvRo_Du_KzgPdkwz=B+595LjKGEv2R0tMXhOBCwojDg@mail.gmail.com>
On Thu, Sep 7, 2017 at 3:59 PM, Claudio Eterno <eterno.claudio@gmail.com> wrote:
> Hello,
> generally I work with a microcontroller that can be compiled in C by
> its specific compiler(C166 family). With this compiler it is possible
> to generate the preprocessed of a file but the output I obtain isn't
> so exaustive like gcc does when I do the same job in linux (gcc -E
> -dD...). Recently I made a test with gcc including paths of the
> C166(so the default headers, instead the linux default libs, are taken
> from the microcontroller directory). The result, apart the built-in
> defines that gcc insert(these can be easily removed with a script), is
> perfect for build a preprocessed header.
> My question: is this usage of gcc a valid use? Should I expect some traps?
> Consider this not a bug but an help request ...
> Thank you,
>
This is the GDB mailing list. You may want to ask on the GCC user
mailing list instead.
I would expect what you want to do to work, but I am slightly confused
as to why you want to do it. You may want to see if SDCC (the small
device C compiler) fits your needs. It may support C166 devices, I
can't tell for sure based on the search results I am seeing.
Cheers,
R0b0t1.
next prev parent reply other threads:[~2017-09-08 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 20:59 Claudio Eterno
2017-09-08 8:02 ` R0b0t1 [this message]
2017-09-08 8:47 ` Claudio Eterno
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=CAAD4mYiYujOYxiEJc91ii+-EJ0Cpgf81qC+EOwfYTQeTMvfWQg@mail.gmail.com \
--to=r030t1@gmail.com \
--cc=eterno.claudio@gmail.com \
--cc=gdb@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