[Bug target/18900] ppc optimization non removable

[Bug target/18900] ppc optimization non removable

[pinskia at gcc dot gnu dot org]

------- Comment #2 from pinskia at gcc dot gnu dot org  2005-11-02 17:16 -------
All P1 enhancements not targeted towards 4.1, moving to P5.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P5


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18900

[Bug target/18900] Don't use fp/vmx regs for mem moves without explicit use of fp/vmx

[amodra at bigpond dot net dot au]

------- Comment #3 from amodra at bigpond dot net dot au  2006-04-11 02:10 -------
The same issue applies to VMX (Altivec) registers.  With lazy fp/vmx task
switching, the first use of fp/vmx regs in a task can be expensive.


-- 

amodra at bigpond dot net dot au changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Should be able to not use fp|Don't use fp/vmx regs for
                   |moves for functions that    |mem moves without explicit
                   |don't implicted use float   |use of fp/vmx
                   |point registers             |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18900

[Bug target/18900] Don't use fp regs for mem moves without explicit use of fp

[pinskia at gcc dot gnu dot org]

------- Comment #4 from pinskia at gcc dot gnu dot org  2006-04-11 02:49 -------
Altivec can be done with -mno-altivec and it is not really a real pain because
if you are going to use altivec registers in your program, you want to use them
more rather than less.  And for the functions you don't want explicit use of
altivec, put them into a seperate file which does not compile with -maltivec
(or compile that seperate file with -mno-altivec since some -mcpu=* enables
altivec).


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Don't use fp/vmx regs for   |Don't use fp regs for mem
                   |mem moves without explicit  |moves without explicit use
                   |use of fp/vmx               |of fp


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18900

[Bug target/18900] Don't use fp regs for mem moves without explicit use of fp

["Thomas Björkman (ÄS/EAB)" <thomas dot bjorkman at ericsson dot com>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]



------- Comment #5 from =?ISO-8859-15?Q?=22Thomas_Bj=F6rkman_=28=C4S/EAB=29=22?=
 <thomas dot bjorkman at ericsson dot com>  2006-04-11 05:10 -------
Subject: Re:  Should be able to not use fp moves for functions
 that don't implicted use float points

Hej !

  How come the slogan on Bug target/18900 has changed from "ppc optimization
non removable"
  to  "Don't use fp regs for mem moves without explicit use of fp" ?

  When will it be corrected ?

  BR / Thomas Björkman


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18900

[Bug target/18900] Don't use fp regs for mem moves without explicit use of fp

[pinskia at gcc dot gnu dot org]

------- Comment #6 from pinskia at gcc dot gnu dot org  2006-08-26 05:14 -------
Actually the easy way for this to be fixed (maybe) is not to allow DImode in
the fp register class.  Though that might fail as we need that to support for
converting between floating point and integers.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18900