Displaying 6 results from an estimated 6 matches for "opt_fno_altivec".
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
...advice for how I can
> > accomplish this?
>
> Off of the top of my head...
>
> Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
>
> if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> CmdArgs.push_back("-backend-option");
> CmdArgs.push_back("-mattr=-altivec");
> }
Perfect, Hal, thanks! That makes good sense. I'll fix this and also
bring some of the CPU handling more up-to-date (several missing
processors...
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
...ts hasn't enlightened me. Any advice for how I can
> accomplish this?
Off of the top of my head...
Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
CmdArgs.push_back("-backend-option");
CmdArgs.push_back("-mattr=-altivec");
}
Why this not done currently I don't know.
-Hal
>
> Thanks! I appreciate any help.
>
> Bill
>
> --
> Bill Schmidt, Ph.D.
> IBM Ad...
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
The problem I'm trying to solve: Invoking clang on PowerPC with
-fno-altivec has no effect.
>From what I've been able to piece together, PPC.td specifies various
CPUs and the processor features available on each. So for example we
have:
def FeatureAltivec : SubtargetFeature<"altivec","HasAltivec", "true",
2013 Jan 31
2
[LLVMdev] Getting command line options to affect subtarget features
...t;
> > > Off of the top of my head...
> > >
> > > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
> > >
> > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> > > CmdArgs.push_back("-backend-option");
> > > CmdArgs.push_back("-mattr=-altivec");
> > > }
> >
> > Perfect, Hal, thanks! That makes good sense. I'll fix this and also
> > bring some of...
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
...accomplish this?
> >
> > Off of the top of my head...
> >
> > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
> >
> > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> > CmdArgs.push_back("-backend-option");
> > CmdArgs.push_back("-mattr=-altivec");
> > }
>
> Perfect, Hal, thanks! That makes good sense. I'll fix this and also
> bring some of the CPU handling more up-to-da...
2013 Jan 31
0
[LLVMdev] Getting command line options to affect subtarget features
...ff of the top of my head...
> > > >
> > > > Within the current infrastructure, I think that we need to alter the Clang PowerPC toolchain code (Clang::AddPPCTargetArgs in Tools.cpp) to do something like this:
> > > >
> > > > if (Args.hasFlag(options::OPT_fno_altivec, options::OPT_faltivec, true)) {
> > > > CmdArgs.push_back("-backend-option");
> > > > CmdArgs.push_back("-mattr=-altivec");
> > > > }
> > >
> > > Perfect, Hal, thanks! That makes good sense. I'll fix this and also...