This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thu, Oct 6, 2011 at 10:45 AM, Yann E. MORIN <yann.morin.1998@anciens.enib.fr> wrote: > Michael, Mike, All, > > On Wednesday 05 October 2011 23:30:53 Michael Hope wrote: >> On Wed, Oct 5, 2011 at 3:14 PM, Mike Frysinger <vapier@gentoo.org> wrote: >> > On Tuesday 04 October 2011 21:21:21 Michael Hope wrote: >> >> It feels a bit funny passing CFLAGS as CXXFLAGS, but the PPL and GCC >> >> target rules already do the same. >> > >> > especially because there are flags valid for the C compiler which are not >> > valid for the C++ compiler ... >> >> Yip. ?There's a good amount of deliberate overlap between the gcc, >> g++, and gfortran flags. ?In crosstool-NG it's currently only used for >> -pipe. > > Yes, it feels icky... But those flags are usually very limited in their > use; currently they're used only for '-pipe'. > > However, with Michael's other patch, it becomes possible for the user to > pass arbitrary flags. But the use case is limited, and focuses on generic > flags. Eg. disabling SSP or fortify, which is documented in the help entry. > > In this case, it's pretty much harmless, I guess... I called the config item 'FLAGS' instead of CFLAGS and documented them as going to both the C and C++ compiler. For my particular (and may other) use cases, there's no need to have a separate entry for C vs C++. -- Michael -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |