From: Basile STARYNKEVITCH <basile@starynkevitch.net>
To: Vikram KS <ksvikram@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: need help on GCC driver
Date: Thu, 30 Jul 2009 14:44:00 -0000 [thread overview]
Message-ID: <4A71B1BB.1020104@starynkevitch.net> (raw)
In-Reply-To: <e075b4df0907300705u154e2af6p9ea4dd2be5ea4454@mail.gmail.com>
Vikram KS wrote:
> Hi,
>
> I have some question on gcc driver.
You really should give more context. Are you doing cross-compilation?
Are you patching the GCC sources? Why do you want to generate a *.sl
file? What are your host & target systems?
>
> Whenever we invoke gcc, it'll pass some default options to the
> compiler, assembler linker etc. But if i dont want to pass all these
> default options but only some of them, what should i do?
>
> For eg: gcc will pass the following option to cc1
>
> /usr/libexec/gcc/i386-redhat-linux/4.1.1/cc1 -quiet -v test.c -quiet
> -dumpbase test.c -mtune=generic -auxbase test -version -o
> /tmp/ccM89Tz7.s
Why are you talking of gcc-4.1.1? It is quite old now! If you want to
patch or hack inside GCC, I strongly suggest working on the trunk
(future gcc-4.5) or on your branch, or at least the latest GCC release
(ie 4.4.1).
>
> and to "as"
>
> as -V -Qy -o /tmp/ccP6YP4n.o /tmp/ccM89Tz7.s
>
> Now i dont want to generate "-o /tmp/ccM89Tz7.s" instead i want to
> generate "/tmp/ccM89Tz7.sl" and this generated ".sl" should be picked
> by my assembler and it should generate the o/p with ".ol" extension.
I suppose it is a typo, and should read with ".sl" extension.
>
> as -V -Qy -o /tmp/ccP6YP4n.ol /tmp/ccM89Tz7.sl
>
> Also if i give "-S" switch, it should generate the the output with the
> ".sl" extension instead of ".s".
>
> Is this possible to do it in "gcc/config/<target>.h" or do i need to
> write a separate spec file.
I don't understand if you have your own target or not. I would suggest
using a spec file (it is probably the easiest way to do). But I am not
very expert on the gcc.c driver!
I really suggest you if possible to avoid hacking gcc 4.1.x and work on
something more recent (otherwise you'll get few help from here...).
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***
next prev parent reply other threads:[~2009-07-30 14:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 14:05 Vikram KS
2009-07-30 14:44 ` Basile STARYNKEVITCH [this message]
2009-07-31 4:37 ` Vikram KS
2009-07-31 5:19 ` Basile STARYNKEVITCH
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=4A71B1BB.1020104@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=gcc@gcc.gnu.org \
--cc=ksvikram@gmail.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).