Displaying 4 results from an estimated 4 matches for "get_subtargetinfo_enum".
2017 Sep 22
2
SchedClasses
...at the microops are less than 20. The ThunderX2 has a detailed cost model for LSE. Could somebody tell me what I am doing wrong?
Cheers,
Tom
#define GET_REGINFO_ENUM
#include "AArch64GenRegisterInfo.inc"
#define GET_INSTRINFO_ENUM
#include "AArch64GenInstrInfo.inc"
#define GET_SUBTARGETINFO_ENUM
#include "AArch64GenSubtargetInfo.inc"
#include "llvm/MC/MCSchedule.h"
#include "llvm/MC/MCRegisterInfo.h"
#include "llvm/MC/MCInstrDesc.h"
#include "llvm/MC/MCInstrInfo.h"
#include "llvm/MC/SubtargetFeature.h"
#include "llvm/MC/MCSu...
2017 Sep 29
0
SchedClasses
...detailed cost model for LSE. Could somebody tell me what I am doing wrong?
>
> Cheers,
> Tom
>
> #define GET_REGINFO_ENUM
> #include "AArch64GenRegisterInfo.inc"
>
> #define GET_INSTRINFO_ENUM
> #include "AArch64GenInstrInfo.inc"
>
> #define GET_SUBTARGETINFO_ENUM
> #include "AArch64GenSubtargetInfo.inc"
>
> #include "llvm/MC/MCSchedule.h"
> #include "llvm/MC/MCRegisterInfo.h"
> #include "llvm/MC/MCInstrDesc.h"
> #include "llvm/MC/MCInstrInfo.h"
> #include "llvm/MC/SubtargetFeature....
2017 Sep 30
1
SchedClasses
...dev <
> llvm-dev at lists.llvm.org> wrote:
> >
>
> >
> > #define GET_REGINFO_ENUM
> > #include "AArch64GenRegisterInfo.inc"
> >
> > #define GET_INSTRINFO_ENUM
> > #include "AArch64GenInstrInfo.inc"
> >
> > #define GET_SUBTARGETINFO_ENUM
> > #include "AArch64GenSubtargetInfo.inc"
> >
> > #include "llvm/MC/MCSchedule.h"
> > #include "llvm/MC/MCRegisterInfo.h"
> > #include "llvm/MC/MCInstrDesc.h"
> > #include "llvm/MC/MCInstrInfo.h"
> > #inclu...
2014 Oct 23
2
[LLVMdev] Target specific info available to Clang (and others)
...hem. If I enable Clang to see them (by adding the include dir on the
path), there will be nothing to stop people from including more than
they should.
The kind of information I want to expose are the enums that identify
features, mainly VFP/NEON/Crypto etc. This is in
ARMGenSubtargetInfo.inc under GET_SUBTARGETINFO_ENUM.
One way I could think of, but it's controversial, is to generate two
files: ARMGenSubtargetInfo.inc and ARMGenSubtargetInfoPublic.inc, the
former in the current directory, the latter in a shared include path
for all tools. That way, not only LLVM, but also Clang, llc, lld etc
would be able t...