public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/18882] [3.3/3.4 Regression] wrong results with complex long double
Date: Thu, 16 Dec 2004 10:23:00 -0000	[thread overview]
Message-ID: <20041216102347.20670.qmail@sourceware.org> (raw)
In-Reply-To: <20041208084814.18882.mikulik@physics.muni.cz>


------- Additional Comments From cvs-commit at gcc dot gnu dot org  2004-12-16 10:23 -------
Subject: Bug 18882

CVSROOT:	/cvs/gcc
Module name:	gcc
Branch: 	gcc-3_4-branch
Changes by:	ebotcazou@gcc.gnu.org	2004-12-16 10:23:32

Modified files:
	gcc            : ChangeLog function.c 
	gcc/testsuite  : ChangeLog 
Added files:
	gcc/testsuite/g++.dg/other: complex1.C 

Log message:
	PR middle-end/18882
	* function.c (assign_stack_local_1): Use BITS_PER_UNIT alignment
	when passed -2 as 'align'.
	(put_var_into_stack): Use 'bool' as the type for the three local
	predicates.  Adjust calls to put_reg_into_stack.
	When passed a CONCAT, instruct put_reg_into_stack to use
	a consecutive stack slot for the second part.
	(put_reg_into_stack): Remove 'promoted_mode' parameter, add
	'consecutive_p' parameter.  Turn the three predicates into 'bool'
	parameters.  Retrieve the register mode from 'reg'.
	When consecutive_p is true, instruct assign_stack_local_1 to use
	BITS_PER_UNIT alignment.
	(put_addressof_into_stack): Use 'bool' as the type for the two
	local predicates. Adjust call to put_reg_into_stack.

Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=2.2326.2.743&r2=2.2326.2.744
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/function.c.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.483.4.22&r2=1.483.4.23
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.3389.2.327&r2=1.3389.2.328
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/g++.dg/other/complex1.C.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=NONE&r2=1.1.2.1



-- 


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


  parent reply	other threads:[~2004-12-16 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08  8:48 [Bug libstdc++/18882] New: wrong results of pow( complex<long double>(2, 1), odd integer ) mikulik at physics dot muni dot cz
2004-12-08  8:54 ` [Bug libstdc++/18882] " mikulik at physics dot muni dot cz
2004-12-08  9:01 ` mikulik at physics dot muni dot cz
2004-12-08 10:19 ` pcarlini at suse dot de
2004-12-08 14:16 ` chris at bubblescope dot net
2004-12-08 14:46 ` [Bug middle-end/18882] [3.3/3.4/4.0? Regression] " pinskia at gcc dot gnu dot org
2004-12-08 14:59 ` pcarlini at suse dot de
2004-12-08 16:28 ` [Bug middle-end/18882] [3.3/3.4 " mikulik at physics dot muni dot cz
2004-12-08 16:29 ` [Bug middle-end/18882] [3.3/3.4 Regression] wrong results with complex long double bangerth at dealii dot org
2004-12-14  9:34 ` ebotcazou at gcc dot gnu dot org
2004-12-14  9:35 ` ebotcazou at gcc dot gnu dot org
2004-12-16 10:23 ` cvs-commit at gcc dot gnu dot org [this message]
2004-12-16 14:08 ` cvs-commit at gcc dot gnu dot org
2004-12-16 14:11 ` ebotcazou at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041216102347.20670.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).