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

[segher at gcc dot gnu.org]

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

Segher Boessenkool  changed:

   What|Removed |Added

 Status|WAITING |RESOLVED
 CC||segher at gcc dot gnu.org
 Resolution|--- |FIXED

--- Comment #8 from Segher Boessenkool  ---
I think a long time ago (early 4.x era?) something went in to always
prefer integer registers for copying.  With the following testcase,
the only floating point use is for the structs with doubles.  (-m32
-mcpu=603 or similar).  Closing as fixed.

===
long long a, b;
struct { int x[2]; } sa, sb;
struct { char x[8]; } ta, tb;
struct { int x; int y; } ua, ub;
struct { float x; float y; } va, vb;
struct { double x; } wa, wb;
struct { double x[1]; } xa, xb;

void f(void)
{
a = b;
sa = sb;
ta = tb;
ua = ub;
va = vb;
wa = wb;
xa = xb;
}
===

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

[msebor at gcc dot gnu.org]

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

Martin Sebor  changed:

   What|Removed |Added

 Status|NEW |WAITING
 CC||msebor at gcc dot gnu.org

--- Comment #7 from Martin Sebor  ---
I haven't been able to reproduce the use of floating point registers in struct
copying with any of my compilers or cross-compilers.  Is there test case that
shows that the problem still exists?

[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

[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

--- 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