- Apr 07, 2010
-
-
Anton Korobeynikov authored
llvm-svn: 100669
-
Anton Korobeynikov authored
llvm-svn: 100668
-
Anton Korobeynikov authored
llvm-svn: 100667
-
Anton Korobeynikov authored
llvm-svn: 100666
-
Anton Korobeynikov authored
llvm-svn: 100665
-
Anton Korobeynikov authored
llvm-svn: 100664
-
Anton Korobeynikov authored
llvm-svn: 100663
-
Anton Korobeynikov authored
llvm-svn: 100662
-
Anton Korobeynikov authored
llvm-svn: 100661
-
Anton Korobeynikov authored
llvm-svn: 100660
-
Anton Korobeynikov authored
llvm-svn: 100659
-
Anton Korobeynikov authored
llvm-svn: 100658
-
Anton Korobeynikov authored
llvm-svn: 100657
-
Anton Korobeynikov authored
llvm-svn: 100656
-
Anton Korobeynikov authored
llvm-svn: 100655
-
Anton Korobeynikov authored
llvm-svn: 100654
-
Anton Korobeynikov authored
llvm-svn: 100653
-
Anton Korobeynikov authored
VHADD differs from VHSUB at least on A9 - the former reads both operands in the second cycle, while the latter reads second operand in first cycle. Introduce new itin classes to catch this behavior. Whether this is true for A8 as well is WIP. llvm-svn: 100652
-
Anton Korobeynikov authored
llvm-svn: 100651
-
Anton Korobeynikov authored
Define new itin classes for ARM <-> VFP reg moves to distinguish from NEON ops. Define proper scheduling itinerary for them on A9. A8 TRM does not specify latency for them at all :( llvm-svn: 100650
-
Anton Korobeynikov authored
llvm-svn: 100649
-
Anton Korobeynikov authored
llvm-svn: 100648
-
Anton Korobeynikov authored
llvm-svn: 100647
-
Anton Korobeynikov authored
Make use of new reserved/required scheduling stuff: introduce VFP and NEON locks to model domain cross stalls precisly. llvm-svn: 100646
-
Anton Korobeynikov authored
llvm-svn: 100643
-
Anton Korobeynikov authored
llvm-svn: 100642
-
Anton Korobeynikov authored
llvm-svn: 100641
-
Sanjiv Gupta authored
llvm-svn: 100601
-
John McCall authored
llvm-svn: 100599
-
Dale Johannesen authored
into AsmPrinter. Target-dependent form is still generated by FastISel and still handled in X86 code. llvm-svn: 100596
-
John McCall authored
solution. The only reason these don't fire with gcc-4.2 is that gcc turns off part of -Wsign-compare in C++ on accident. llvm-svn: 100581
-
Dale Johannesen authored
llvm-svn: 100578
-
Dale Johannesen authored
There is probably a more elegant way to do this. llvm-svn: 100573
-
Bob Wilson authored
Radar 7770501. llvm-svn: 100568
-
- Apr 06, 2010
-
-
Jim Grosbach authored
When a frame pointer is not otherwise required, and dynamic stack alignment is necessary solely due to the spilling of a register with larger alignment requirements than the default stack alignment, the frame pointer can be both used as a general purpose register and a frame pointer. That goes poorly, for obvious reasons. This patch brings back a bit of old logic for identifying the use of such registers and conservatively reserves the frame pointer during register allocation in such cases. For now, implement for X86 only since it's 32-bit linux which is hitting this, and we want a targeted fix for 2.7. As a follow-on, this will be expanded to handle other targets, as theoretically the problem could arise elsewhere as well. llvm-svn: 100559
-
Jakob Stoklund Olesen authored
This fixes the Bullet regression on i386/nocona. llvm-svn: 100553
-
Jakob Stoklund Olesen authored
Operand 2 on a load instruction does not have to be a RegisterSDNode for this to work. llvm-svn: 100497
-
Evan Cheng authored
llvm-svn: 100480
-
- Apr 05, 2010
-
-
Eric Christopher authored
llvm-svn: 100466
-
Chris Lattner authored
isn't well specified. ARM really needs to have its instprinter finished at some point. llvm-svn: 100439
-