- Jun 23, 2010
-
-
Eric Christopher authored
llvm-svn: 106677
-
Rafael Espindola authored
having a library both as bitcode and native code. We want to use the bitcode first, but if codegen produces new undefined references we have to use the native code to satisfy those references. Gold has no notion of bitcode and native search directories, so instead it has an API where the plugin can instruct it to look for the libraries it is passing to it. This patch uses that API. llvm-svn: 106674
-
Bruno Cardoso Lopes authored
llvm-svn: 106672
-
Nico Weber authored
llvm-svn: 106671
-
Bruno Cardoso Lopes authored
Given the pattern below as an example: list<dag> Pattern = [(set RC:$dst, (v4f32 (shufp:src3 RC:$src1, (mem_frag addr:$src2))))]; The right reference resolving should lead to: list<dag> Pattern = [(set VR128:$dst, (v4f32 (shufp:src3 VR128:$src1, (mem_frag addr:$src2))))]; But was yielding: list<dag> Pattern = [(set VR128:$dst, (v4f32 (shufp VR128:$src1, (mem_frag addr:$src2))))]; Fix this by passing the right name when creating a new DagInit node. llvm-svn: 106670
-
Duncan Sands authored
llvm-svn: 106668
-
Sean Callanan authored
errors pointed out by John McCall. llvm-svn: 106665
-
Dale Johannesen authored
llvm-svn: 106664
-
Dale Johannesen authored
llvm-svn: 106663
-
Dale Johannesen authored
branch turns out to be ARM-to-Thumb or vice versa the linker cannot resolve this. 8120438. If this optimization is going to be useful we probably need a compiler flag "assume callees are same architecture" or something like that. llvm-svn: 106662
-
Daniel Dunbar authored
llvm-svn: 106661
-
Bill Wendling authored
into the same node, but with different non-memory operands, we need to replace the memory operands after it's finished morphing. llvm-svn: 106643
-
Daniel Dunbar authored
all the kinks are worked out. llvm-svn: 106641
-
Ted Kremenek authored
llvm-svn: 106640
-
Daniel Dunbar authored
llvm-svn: 106639
-
Daniel Dunbar authored
llvm-svn: 106638
-
Daniel Dunbar authored
Revert r106263, "Fold the ShrinkDemandedOps pass into the regular DAGCombiner pass,"... it was causing both 'file' (with clang) and 176.gcc (with llvm-gcc) to be miscompiled. llvm-svn: 106634
-
Jim Grosbach authored
to using that. llvm-svn: 106633
-
Jim Grosbach authored
MEMBARRIER fences aren't necessary for ARM. Tell the combiner to fold them away. llvm-svn: 106631
-
Jim Grosbach authored
atomic intrinsics, either because the use locking instructions for the atomics, or because they perform the locking directly. Add support in the DAG combiner to fold away the fences. llvm-svn: 106630
-
Sebastian Redl authored
llvm-svn: 106629
-
Jim Grosbach authored
llvm-svn: 106628
-
Jakob Stoklund Olesen authored
llvm-svn: 106627
-
Gabor Greif authored
llvm-svn: 106626
-
Argyrios Kyrtzidis authored
llvm-svn: 106625
-
Argyrios Kyrtzidis authored
Modify ClassTemplateSpecializationDecl and ClassTemplatePartialSpecializationDecl to allow PCH read/write. llvm-svn: 106624
-
Gabor Greif authored
llvm-svn: 106623
-
Gabor Greif authored
llvm-svn: 106622
-
Eric Christopher authored
llvm-svn: 106621
-
Nick Lewycky authored
Haiku like Linux provides <regex.h>, so use it. Patch by Paul Davey! llvm-svn: 106620
-
Chris Lattner authored
with several tweaks by me. llvm-svn: 106619
-
Chris Lattner authored
llvm-svn: 106618
-
Zhongxing Xu authored
llvm-svn: 106617
-
Zhongxing Xu authored
llvm-svn: 106616
-
Greg Clayton authored
to the debugger from GUI windows. Previously there was one global debugger instance that could be accessed that had its own command interpreter and current state (current target/process/thread/frame). When a GUI debugger was attached, if it opened more than one window that each had a console window, there were issues where the last one to setup the global debugger object won and got control of the debugger. To avoid this we now create instances of the lldb_private::Debugger that each has its own state: - target list for targets the debugger instance owns - current process/thread/frame - its own command interpreter - its own input, output and error file handles to avoid conflicts - its own input reader stack So now clients should call: SBDebugger::Initialize(); // (static function) SBDebugger debugger (SBDebugger::Create()); // Use which ever file handles you wish debugger.SetErrorFileHandle (stderr, false); debugger.SetOutputFileHandle (stdout, false); debugger.SetInputFileHandle (stdin, true); // main loop SBDebugger::Terminate(); // (static function) SBDebugger::Initialize() and SBDebugger::Terminate() are ref counted to ensure nothing gets destroyed too early when multiple clients might be attached. Cleaned up the command interpreter and the CommandObject and all subclasses to take more appropriate arguments. llvm-svn: 106615
-
Daniel Dunbar authored
Revert r106066, "Create a more targeted fix for not sinking instructions into a range where it"... it causes bzip2 to be miscompiled by Clang. Conflicts: lib/CodeGen/MachineSink.cpp llvm-svn: 106614
-
Sean Callanan authored
looking for external variables. Also cleaned up the log messages coming from the DWARF interpreter. llvm-svn: 106613
-
Stuart Hastings authored
llvm-svn: 106611
-
Ted Kremenek authored
crash reported in PR 7450. llvm-svn: 106609
-
Eric Christopher authored
Thanks Daniel! llvm-svn: 106608
-