On Tue, May 03, 2011 at 10:51:51PM -0400, David Edelsohn wrote:
What does this do to the ABI? Haven't we now broken the ABI and
broken backwards compatibility?
In this case, GCC wasn't following the ABI. My patch will have GCC follow the
ABI. The XL compiler also follows the ABI. So we have
On Wed, May 04, 2011 at 11:33:43AM +0200, Richard Guenther wrote:
On Wed, May 4, 2011 at 4:51 AM, David Edelsohn dje@gmail.com wrote:
What does this do to the ABI? Haven't we now broken the ABI and
broken backwards compatibility?
It at least looks like so. You need to add appropriate
On Tue, May 3, 2011 at 5:27 PM, Michael Meissner
meiss...@linux.vnet.ibm.com wrote:
When I added VSX support to the powerpc, I overlooked passing and return
V2DImode arguments, since the only machine operation that supports V2DI is
vector floating point conversion. Consequentally, V2DI types
On Wed, May 4, 2011 at 4:51 AM, David Edelsohn dje@gmail.com wrote:
On Tue, May 3, 2011 at 5:27 PM, Michael Meissner
meiss...@linux.vnet.ibm.com wrote:
When I added VSX support to the powerpc, I overlooked passing and return
V2DImode arguments, since the only machine operation that
On Wed, 2011-05-04 at 11:33 +0200, Richard Guenther wrote:
On Wed, May 4, 2011 at 4:51 AM, David Edelsohn dje@gmail.com wrote:
On Tue, May 3, 2011 at 5:27 PM, Michael Meissner
meiss...@linux.vnet.ibm.com wrote:
This patch fixes that so that V2DImode values are passed and returned
On Tue, May 3, 2011 at 5:27 PM, Michael Meissner
meiss...@linux.vnet.ibm.com wrote:
When I added VSX support to the powerpc, I overlooked passing and return
V2DImode arguments, since the only machine operation that supports V2DI is
vector floating point conversion. Consequentally, V2DI types
