Displaying 6 results from an estimated 6 matches for "modernish".
2013 Nov 10
0
[LLVMdev] [cfe-dev] Goal for 3.5: Library-friendly headers
...t care about the
> definition, maybe embedding applications or OS headers do?
Given that 3 of the 5 #undefs are directly relevant for me -- they exist
because OS headers and/or compiler default configurations provide legacy
macros that can't easily be dropped without breaking old cruft. All
modernish software is supposed to use the corresponding __ version of
the names.
INT64_MAX as seen by the context is about a AIX specific header bug.
alloca has a comment about VC++. Might be better to add a conditional
around it and see if that solves the problem.
In short, I don't see a real problem...
2013 Nov 10
8
[LLVMdev] Goal for 3.5: Library-friendly headers
With the recent thread on using C++11 in LLVM/clang, one of the
recurring themes was a desire to make the internal headers more consumable.
While I don't personally want any kind of stability guarantee for
internal headers, I do think we can do more to ensure that any given
snapshot of the headers is consumable from different compilers and build
configurations.
In practice this means
2013 Nov 10
1
[LLVMdev] [cfe-dev] Goal for 3.5: Library-friendly headers
...t; definition, maybe embedding applications or OS headers do?
> Given that 3 of the 5 #undefs are directly relevant for me -- they exist
> because OS headers and/or compiler default configurations provide legacy
> macros that can't easily be dropped without breaking old cruft. All
> modernish software is supposed to use the corresponding __ version of
> the names.
As an extra data point, clang itself pre-defines PSP, qdsp6, hexagon and
MSP430, and it looks from a web search that platform compilers have a
tradition of defining the platform and architecture like this so the
only reaso...
2011 Jul 28
0
[LLVMdev] Is using lots of in-register values in IR bad?
...al operations that, for example, vector machines of the '60's
and '70's implemented directly. Extract/insert from/to variable index
being one of them. Extractvalue is a little more complicated, of
course, but special cases of it are implemented on x86 (for example) and
other "modernish" targets.
For cases like these, it is best to create a target-specific intrinsic
and use that to represent the operation. For operations not implemented
directly by the target, an alloca+GEP may be necessary.
> Some things seem to be possible only by bitcasting pointers, e.g.
> splitt...
2011 Jul 11
9
Centos 6 Server has no GUI
Hi,
So first daft question with Centos 6 (someone had to be first!) I've setup Centos 6 as a Server but as with Centos 5 it used to boot into the GUI but v6 doesn't do this, startx etc doesn't seem to work to launch the GUI
Any suggestions on how I can get this to work?
Thank you
Keith
2011 Jul 28
4
[LLVMdev] Is using lots of in-register values in IR bad?
Hi,
I'm a newbie when it comes to compilers (and even close-to-machine coding),
but recently started working on my own language and am using LLVM as the
mid/backend. Currently I'm generating .ll files from a front-end written in
Scala. The language is not really serious, just a way to learn more about
compilers (and LLVM) and maybe serve as a base for further experiments. It's