[Bug rtl-optimization/20242] Pessimizing effects of defining EXTRA_MEMORY_CONSTRAINT

2005-02-27 Thread hp at gcc dot gnu dot org
--- Additional Comments From hp at gcc dot gnu dot org 2005-02-28 02:52 --- (1) Is URL:http://gcc.gnu.org/ml/gcc-patches/2005-02/msg01769.html and doesn't contain the atomicity.h patch. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20242

[Bug rtl-optimization/20242] Pessimizing effects of defining EXTRA_MEMORY_CONSTRAINT

2005-02-27 Thread hp at gcc dot gnu dot org
--- Additional Comments From hp at gcc dot gnu dot org 2005-02-28 02:56 --- Created an attachment (id=8293) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8293action=view) test.ps Minimal ghostscript input file for noticing performance regression. --

[Bug rtl-optimization/20242] Pessimizing effects of defining EXTRA_MEMORY_CONSTRAINT

2005-02-27 Thread hp at gcc dot gnu dot org
--- Additional Comments From hp at gcc dot gnu dot org 2005-02-28 03:01 --- Created an attachment (id=8294) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8294action=view) bigfun.i Test-case. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20242

[Bug rtl-optimization/20242] Pessimizing effects of defining EXTRA_MEMORY_CONSTRAINT

2005-02-27 Thread hp at gcc dot gnu dot org
--- Additional Comments From hp at gcc dot gnu dot org 2005-02-28 03:06 --- Created an attachment (id=8295) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8295action=view) baseline Generated code before (1) and also if *only* the EXTRA_MEMORY_CONSTRAINT is removed. --

[Bug rtl-optimization/20242] Pessimizing effects of defining EXTRA_MEMORY_CONSTRAINT

2005-02-27 Thread hp at gcc dot gnu dot org
--- Additional Comments From hp at gcc dot gnu dot org 2005-02-28 03:11 --- Created an attachment (id=8296) -- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8296action=view) diff -up baseline.s fixed-Q-and-E_M_C.s Diff showing regressing change in generated assembly code. --

[Bug target/19065] Make CRIS libstdc++ asms autoincrement-safe

2005-02-27 Thread hp at gcc dot gnu dot org
-- What|Removed |Added Target Milestone|--- |4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19065

[Bug c/20243] New: static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread schlie at comcast dot net
Although functional, the limited read/write memory is needless used to redundantly store static read-only initialization data/strings effectively eliminates this memory from having any useful purpose. main.elf: file format elf32-avr Sections: Idx Name Size VMA LMA

[Bug target/20243] static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-28 04:07 --- Huh? -- What|Removed |Added Component|c |target

[Bug target/20243] static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-28 04:11 --- I assume you are talking about the following code: /* __do_copy_data is only necessary if there is anything in .data section. Does not use RAMPZ - crt*.o provides a replacement for 64K devices. */

[Bug target/20243] static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-28 04:14 --- And this fixme: /* FIXME: output these only if there is anything in the .data / .bss sections - some code size could be saved by not linking in the initialization code from libgcc if one or both

[Bug target/18145] Do not emit __do_copy_data or __do_clear_bss if .data or .bss is empty.

2005-02-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-28 04:14 --- *** Bug 20243 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug target/20243] static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread schlie at comcast dot net
--- Additional Comments From schlie at comcast dot net 2005-02-28 04:24 --- (In reply to comment #3) *** This bug has been marked as a duplicate of 18145 *** sorry, no. - that bug says don't copy when there's no data to copy. - this bug says, don't static read-only data even if

[Bug target/20243] static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-28 04:28 --- (In reply to comment #4) (In reply to comment #3) *** This bug has been marked as a duplicate of 18145 *** sorry, no. oh, this is still a target bug. -- What|Removed

[Bug target/20243] static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread schlie at comcast dot net
--- Additional Comments From schlie at comcast dot net 2005-02-28 04:40 --- oh, this is still a target bug. Possibly (but likely of similar concern for other small embedded targets) The problem is that the initialization data which is linked in .data (stored in readable flash/rom)

[Bug target/20243] static initialization .data redundantly copied to ram prior to use.

2005-02-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-28 04:46 --- Yes because MOVE_RATIO is too low for avr really. But there might different issues here really, one is for an example MOVE_RATIO is too low which causes the addition of the .data stuff but the other is

[Bug fortran/5900] [g77 gfortran] Lapack regressions since g77 2.95.2

2005-02-27 Thread billingd at gcc dot gnu dot org
--- Additional Comments From billingd at gcc dot gnu dot org 2005-02-28 05:13 --- With cygwin gfortran-4.0 20050227 at -O0 I get excellent results: csep.out: CST:1 out of 4662 tests failed to pass the threshold csep.out: CST:2 out of 4662 tests failed to pass the threshold

[Bug c++/19948] [4.0/4.1 Regression] ICE: tree check: expected class 'declaration', have 'exceptional' (error_mark) in pushtag, at cp/name-lookup.c:4658

2005-02-27 Thread lerdsuwa at gcc dot gnu dot org
--- Additional Comments From lerdsuwa at gcc dot gnu dot org 2005-02-28 06:22 --- If you want a work around, simply use this in the first 'friend' declaration: friend class util::persistent_object_manager; There is still uncertainty about whether name from 'using'

[Bug libfortran/17748] libgfortran contains undefined references to _environ

2005-02-27 Thread cvs-commit at gcc dot gnu dot org
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-02-28 06:35 --- Subject: Bug 17748 CVSROOT:/cvs/gcc Module name:gcc Branch: gcc-4_0-branch Changes by: [EMAIL PROTECTED] 2005-02-28 06:34:55 Modified files: libgfortran:

<    1   2