[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Comment #8 from gdr at gcc dot gnu dot org 2007-02-03 15:31 --- won't fix in GCC-4.0.4 -- gdr at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||WONTFIX http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Comment #7 from gdr at gcc dot gnu dot org 2007-01-18 03:11 --- Won't fix for GCC-4.0.x -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
-- mmitchel at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|4.0.3 |4.0.4 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Comment #6 from janis at gcc dot gnu dot org 2006-01-05 17:52 --- My nightly build compilers don't show errors or warnings from anything later than 3.4: elm3b11% /opt/gcc-nightly/trunk/bin/gcc -c -mno-altivec -mabi=altivec 18631.c elm3b11% /opt/gcc-nightly/4.1/bin/gcc -c -mno-altivec -mabi=altivec 18631.c elm3b11% /opt/gcc-nightly/4.0/bin/gcc -c -mno-altivec -mabi=altivec 18631.c elm3b11% /opt/gcc-nightly/3.4/bin/gcc -c -mno-altivec -mabi=altivec 18631.c 18631.c: In function `ret': 18631.c:3: error: Cannot return value in vector register because altivec instructions are disabled, use -maltivec to enable them. 18631.c: In function `pass': 18631.c:4: error: Cannot pass argument in vector register because altivec instructions are disabled, use -maltivec to enable them. Results are the same with -Wall, and for trunk on 20051002 and 20051030. Andrew, what options did you use to get the warnings shown in comment #3, and was that with powerpc*-*-linux*? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Comment #5 from bonzini at gnu dot org 2006-01-04 08:57 --- Janis, can you confirm this is fixed on 4.0? -- bonzini at gnu dot org changed: What|Removed |Added Status|NEW |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Comment #4 from paolo dot bonzini at lu dot unisi dot ch 2005-10-22 09:52 --- Subject: Re: [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec I *think* it is also fixed on 4.0; a grep for the error message in config/rs6000/rs6000.c would confirm or deny this. Paolo -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Comment #3 from pinskia at gcc dot gnu dot org 2005-10-22 03:36 --- Fixed at least on the mainline: t.c: In function 'ret': t.c:3: warning: GCC vector returned by reference: non-standard ABI extension with no compatibility guarantee t.c: In function 'pass': t.c:4: warning: GCC vector passed by reference: non-standard ABI extension with no compatibility guarantee -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Summary|[4.0/4.1 Regression] missing|[4.0 Regression] missing |error messages passing |error messages passing |vectors with -mno-altivec - |vectors with -mno-altivec - |mabi=altivec|mabi=altivec http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Additional Comments From janis187 at us dot ibm dot com 2004-11-24 16:53 --- Oops, in the submission I said There used to be error messages for passing vectors by value or returning vectors from functions if AltiVec support was on but the non-AltiVec ABI was used. That should be: There used to be error messages ... if AltiVec support was not on and the AltiVec ABI was used. The AltiVec ABI says that vectors that map to hardware vectors are passed in vector registers. That variant of the ABI is the default but can be turned off with -mabi=no-altivec, which is useful for binary compatibility with modules that will be used on multiple types of PowerPC-64 hardware. The ABI doesn't cover generic vectors that don't map to hardware vectors, but GCC passes them by reference for either variant of the ABI. It probably doesn't specifically cover the case of generic vectors that map to hardware vectors when AltiVec support isn't enabled, but that seems surprising enough that it ought to continue to be an error. I personally think it ought to be an error to pass any synthetic vector by value unless it is specifically covered by the ABI, but that's another mess that no one wants to touch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
[Bug target/18631] [4.0 Regression] missing error messages passing vectors with -mno-altivec -mabi=altivec
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-11-24 06:18 --- Confirmed, I really don't think this should be an error as on darwin like ppc64-linux the ABI defaults to the altivec ABI so there is no way to return generic vector on darwin or ppc64-linux. -- What|Removed |Added Status|UNCONFIRMED |NEW Ever Confirmed||1 Keywords||diagnostic Last reconfirmed|-00-00 00:00:00 |2004-11-24 06:18:55 date|| Summary|missing error messages |[4.0 Regression] missing |passing vectors with -mno- |error messages passing |altivec -mabi=altivec |vectors with -mno-altivec - ||mabi=altivec Target Milestone|--- |4.0.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18631
