- Jan 16, 2013
-
-
Tim Northover authored
llvm-svn: 172650
-
Eric Christopher authored
initializations to fix Wreorder warning. llvm-svn: 172649
-
Eric Christopher authored
llvm-svn: 172648
-
Greg Clayton authored
llvm-svn: 172647
-
Eric Christopher authored
llvm-svn: 172646
-
Michael J. Spencer authored
Patch by Jakub Staszak. llvm-svn: 172645
-
Michael J. Spencer authored
llvm-svn: 172644
-
Aaron Ballman authored
Adding verbiage to the Language Extensions document about __has_include and __has_include_next only being allowed within preprocessor directives. llvm-svn: 172643
-
Eli Bendersky authored
llvm-svn: 172642
-
Enrico Granata authored
llvm-svn: 172641
-
Eli Bendersky authored
llvm-svn: 172640
-
Aaron Ballman authored
No longer crashing with an assert when __has_include or __has_include_next is used outside of a preprocessor directive. This fixes PR14837. llvm-svn: 172639
-
Eli Bendersky authored
llvm-svn: 172638
-
Eli Bendersky authored
return into the safe harbor of AsmParser's private areas. llvm-svn: 172637
-
rdar://problem/13021266Enrico Granata authored
Adding FindFirstGlobalVariable to SBModule and SBTarget These calls work like FindGlobalVariables but they only return the first match found and so they can return an SBValue instead of an SBValueList for added convenience of use llvm-svn: 172636
-
Douglas Gregor authored
when the methods are declared in a submodule that has not yet been imported. Part of <rdar://problem/10634711>. llvm-svn: 172635
-
Daniel Dunbar authored
- Instead of computing a bunch of buckets of different flag types, just do an incremental link resolving conflicts as they arise. - This also has the advantage of making the link result deterministic and not dependent on map iteration order. llvm-svn: 172634
-
Enrico Granata authored
Greg created a new API on SBProcess to get an ID that is guaranteed to be unique even in situations where underlying platforms would actually duplicate or hardcode PIDs The Python data formatters use a per-process cache that was previously keying off the PID. Moving that to be based on this new notion of unique ID. llvm-svn: 172633
-
Argyrios Kyrtzidis authored
null before using it. llvm-svn: 172632
-
Howard Hinnant authored
Make a few tests optimization-proof. These tests were failing under -O3 because the optimizer was eliminating the call to new. llvm-svn: 172631
-
Kevin Enderby authored
AT_producer. Which includes clang's version information so we can tell which version of the compiler was used. This is the first of two steps to allow us to do that. This is the llvm-mc change to provide a method to set the AT_producer string. The second step, coming soon to a clang near you, will have the clang driver pass the value of getClangFullVersion() via an flag when invoking the integrated assembler on assembly source files. rdar://12955296 llvm-svn: 172630
-
Argyrios Kyrtzidis authored
while deserializing a macro, make sure to copy/move what we need from it. Fixes clang-x86_64-debian-fast bot. llvm-svn: 172629
-
rdar://problem/13009943Greg Clayton authored
Added a unique integer identifier to processes. Some systems, like JTAG or other simulators, might always assign the same process ID (pid) to the processes that are being debugged. In order for scripts and the APIs to uniquely identify the processes, there needs to be another ID. Now the SBProcess class has: uint32_t SBProcess::GetUniqueID(); This integer ID will help to truly uniquely identify a process and help with appropriate caching that can be associated with a SBProcess object. llvm-svn: 172628
-
Peter Collingbourne authored
In r143502, we renamed getHostTriple() to getDefaultTargetTriple() as part of work to allow the user to supply a different default target triple at configure time. This change also affected the JIT. However, it is inappropriate to use the default target triple in the JIT in most circumstances because this will not necessarily match the current architecture used by the process, leading to illegal instruction and other such errors at run time. Introduce the getProcessTriple() function for use in the JIT and its clients, and cause the JIT to use it. On architectures with a single bitness, the host and process triples are identical. On other architectures, the host triple represents the architecture of the host CPU, while the process triple represents the architecture used by the host CPU to interpret machine code within the current process. For example, when executing 32-bit code on a 64-bit Linux machine, the host triple may be 'x86_64-unknown-linux-gnu', while the process triple may be 'i386-unknown-linux-gnu'. This fixes JIT for the 32-on-64-bit (and vice versa) build on non-Apple platforms. Differential Revision: http://llvm-reviews.chandlerc.com/D254 llvm-svn: 172627
-
Reed Kotler authored
Waiting for new llvm attribute code for the next step. llvm-svn: 172626
-
Argyrios Kyrtzidis authored
set on the cursor; return a null type in such a case. llvm-svn: 172625
-
Daniel Jasper authored
Before: Constructor() : a(a), // comment a(a) {} After: Constructor() : a(a), // comment a(a) {} Needed this as a quick fix. Will add more tests for this in a future commit. llvm-svn: 172624
-
Argyrios Kyrtzidis authored
Patch by Enea Zaffanella! llvm-svn: 172623
-
Eli Bendersky authored
llvm-svn: 172622
-
Daniel Jasper authored
We used to incorrectly parse aaaaaa ? aaaaaa(aaaaaa) : aaaaaaaa; Due to an l_paren being followed by a colon, we assumed it to be part of a constructor initializer. Thus, we never found the colon belonging to the conditional expression, marked the line as bing incorrect and did not format it. llvm-svn: 172621
-
Argyrios Kyrtzidis authored
Previously we would serialize the macro redefinitions as a list, part of the identifier, and try to chain them together across modules individually without having the info that they were already chained at definition time. Change this by serializing the macro redefinition chain and then try to synthesize the chain parts across modules. This allows us to correctly pinpoint when 2 different definitions are ambiguous because they came from unrelated modules. Fixes bogus "ambiguous expansion of macro" warning when a macro in a PCH is redefined without undef'ing it first. rdar://13016031 llvm-svn: 172620
-
Daniel Jasper authored
Before: int x = ** a; After: int x = **a; llvm-svn: 172619
-
Daniel Jasper authored
Various reasons seem to speak against it, so I am disabling this for now. Changed tests to still test this option. llvm-svn: 172618
-
Daniel Jasper authored
"Bin-packing" here means allowing multiple parameters on one line, if a function call/declaration is spread over multiple lines. This is required by the Chromium style guide and probably desired for the Google style guide. Not making changes to LLVM style as I don't have enough data. With this enabled, we format stuff like: aaaaaaaaaaaaaaa(aaaaaaaaaa, aaaaaaaaaa, aaaaaaaaaaaaaaaaaaaaaaa).aaaaaaaaaaaaaaaaaa(); llvm-svn: 172617
-
Manuel Klimek authored
llvm-svn: 172616
-
Evgeniy Stepanov authored
llvm-svn: 172615
-
Evgeniy Stepanov authored
llvm-svn: 172614
-
Dmitry Vyukov authored
llvm-svn: 172613
-
Benjamin Kramer authored
llvm-svn: 172612
-
Benjamin Kramer authored
Should fix the arm buildbot (which only builds the arm target). llvm-svn: 172611
-