This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Any plans to add separate flags for dealing with assembly code?
- From: "sandeep" <sandeep at codito dot com>
- To: "\"ecos-mailing-list\"" <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 13 Nov 2003 19:57:07 +0530
- Subject: [ECOS] Any plans to add separate flags for dealing with assembly code?
- Organization: Codito Technologies Pvt. Ltd.
Hi,
I looked through ecos repository and find CC and ACTUAL_CFLAGS are being used
for dealing with *.S files. Right! there will be handful of *.S files in any
ecos build, mainly going under hal, but it would be better if AS and
ACTUAL_ASFLAGS are maintained separately for dealing with assembly sources, thus
having more flexibility to tweak the flags as needed.
For example in a situation --
AS could be same as CC
but some CFLAGS combination might be causing trouble dealing with assembly
sources based on toolchain, so requirement could be something like
CFLAGS = opt1 opt2 opt3
ASFLAGS = opt1 opt3 opt4
One way currently is to do some tweaking hacks in rules.mak . Are there any
better and cleaner alternatives?
*.S files could also be part of application code as well, so it is more than hal
issue.
regards
sandeep
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss