[Bug c++/36547] New: internal compiler error: Segmentation fault
This works with "gcc", but not with "g++":
int main()
{
const char *x[] = (const char *[]){ "test","blabla" };
}
--
Summary: internal compiler error: Segmentation fault
Product: gcc
Version: 3.4.5
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ninive at gmx dot at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36547
[Bug c++/36547] internal compiler error: Segmentation fault
--- Comment #1 from paolo dot carlini at oracle dot com 2008-06-16 08:43 --- This doesn't ICE anymore with current maintained GCCs (4_2, 4_3, mainline). -- paolo dot carlini at oracle dot com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36547
[Bug target/36527] gcc 4.2.x generates wrong code for ARM target
--- Comment #7 from benny at ammitzboell-consult dot dk 2008-06-16 09:10 --- test.c also fails with gcc 3.4.6 - testcpp.cpp however works with gcc 3.4.6. -- benny at ammitzboell-consult dot dk changed: What|Removed |Added Severity|normal |major Known to fail|4.2.3 4.2.4 |4.2.3 4.2.4 3.4.6 Known to work||3.4.6 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36527
[Bug c++/36547] internal compiler error: Segmentation fault
--- Comment #2 from ninive at gmx dot at 2008-06-16 09:11 --- You are right. Sorry for disturbing. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36547
[Bug middle-end/32492] [4.3 Regression] attribute always_inline -> sorry, unimplemented: recursive inlining
--- Comment #17 from josep dot m dot perez at bsc dot es 2008-06-16 09:23
---
I've reproduced the same problem with official GCC 4.3.1 on Linux amd64.
template
struct B {
struct C {
__attribute__((always_inline)) C(C const &c)
{
}
};
void __attribute__((always_inline)) g(C c)
{
}
};
void trigger(B b, B::C c)
{
b.g(c);
}
Using built-in specs.
Target: x86_64-unknown-linux-gnu
Configured with: ./configure --prefix=/opt/gcc-4.3.1
Thread model: posix
gcc version 4.3.1 (GCC)
COLLECT_GCC_OPTIONS='-c' '-v' '-shared-libgcc' '-mtune=generic'
/opt/gcc-4.3.1/libexec/gcc/x86_64-unknown-linux-gnu/4.3.1/cc1plus
-fpreprocessed Cleanup4.ii -quiet -dumpbase Cleanup4.ii -mtune=generic -auxbase
Cleanup4 -version -o /tmp/ccJPmqDW.s
GNU C++ (GCC) version 4.3.1 (x86_64-unknown-linux-gnu)
compiled by GNU C version 4.3.1, GMP version 4.2.2, MPFR version 2.3.1.
GGC heuristics: --param ggc-min-expand=98 --param ggc-min-heapsize=128607
Compiler executable checksum: 24d9f1589345aaa01dede2a12dd4f7be
Cleanup4.ii: In function 'void trigger(B, B::C)':
Cleanup4.ii:8: sorry, unimplemented: inlining failed in call to 'void
B::g(B::C) [with T = int]': recursive inlining
Cleanup4.ii:15: sorry, unimplemented: called from here
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32492
[Bug tree-optimization/36493] [4.3/4.4 Regression] vectorizer aliasing bug
--- Comment #3 from irar at gcc dot gnu dot org 2008-06-16 10:39 --- Subject: Bug 36493 Author: irar Date: Mon Jun 16 10:39:07 2008 New Revision: 136843 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136843 Log: PR tree-optimization/36493 * tree-vect-transform.c (vect_create_data_ref_ptr): Remove TYPE from the arguments list. Use VECTYPE to create vector pointer. (vectorizable_store): Fail if accesses through a pointer to vectype do not alias the original memory reference operands. Call vect_create_data_ref_ptr without the removed argument. (vectorizable_load): Likewise. (vect_setup_realignment): Call vect_create_data_ref_ptr without the removed argument. Added: trunk/gcc/testsuite/gcc.dg/vect/pr36493.c Modified: trunk/gcc/ChangeLog trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-vect-transform.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36493
[Bug tree-optimization/36493] [4.3/4.4 Regression] vectorizer aliasing bug
--- Comment #4 from irar at gcc dot gnu dot org 2008-06-16 10:43 --- Subject: Bug 36493 Author: irar Date: Mon Jun 16 10:42:56 2008 New Revision: 136844 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136844 Log: PR tree-optimization/36493 * tree-vect-transform.c (vect_create_data_ref_ptr): Remove TYPE from the arguments list. Use VECTYPE to create vector pointer. (vectorizable_store): Fail if accesses through a pointer to vectype do not alias the original memory reference operands. Call vect_create_data_ref_ptr without the removed argument. (vectorizable_load): Likewise. (vect_setup_realignment): Call vect_create_data_ref_ptr without the removed argument. Added: branches/gcc-4_3-branch/gcc/testsuite/gcc.dg/vect/pr36493.c Modified: branches/gcc-4_3-branch/gcc/ChangeLog branches/gcc-4_3-branch/gcc/testsuite/ChangeLog branches/gcc-4_3-branch/gcc/tree-vect-transform.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36493
[Bug c/32415] libgcc_s not found in library search path with --enable-version-specific-runtime-libs
--- Comment #7 from jwakely dot gcc at gmail dot com 2008-06-16 11:12 --- This has now been broken for at least 3 releases and is going to stay broken in 4.4 at this rate. Could a build maintainer comment on Richard's analysis in bug 35248? CCing Paolo again. -- jwakely dot gcc at gmail dot com changed: What|Removed |Added CC||bonzini at gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32415
[Bug other/31754] Include column number along line in error messages main.cpp:5:38
--- Comment #2 from dseketel at redhat dot com 2008-06-16 11:13 --- Created an attachment (id=15774) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15774&action=view) produce more accurate column information in error messages This patch modifies the c++ parser to produce more accurate column information in error messages. The basic idea of the patch is to not use the global input_location variable to generate line/columns info in error messages, but rather to pass the right token location to each error message. For now, I have mostly touched only the parsing code. Semantic analysis code has not been touched yet. I have not touched warning generation code either. I have started to make the error tests in testsuite/g++.dg/parse/ be column aware by forcing the -fshow-column flag on these tests as well. It is looking good so far. I realised that -fno-show-column was forced in gcc/testsuite/lib/g++.exp. So I commented that so that -fshow-column flag can take effect when triggered. This patch is work in progress and I will update it here until it becomes solid enought to be posted to the gcc-patches mailing list. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31754
[Bug other/31754] Include column number along line in error messages main.cpp:5:38
--- Comment #3 from dseketel at redhat dot com 2008-06-16 11:15 --- I forgot to say that my patch just affects the c++ front end of gcc. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31754
[Bug c++/33435] internal compiler error with templates and openmp
--- Comment #5 from bangerth at dealii dot org 2008-06-16 15:03 --- This appears to work for me now with gcc version 4.4.0 20080527 (experimental) [trunk revision 136055] (GCC) Can you check whether it also works for you? W. -- bangerth at dealii dot org changed: What|Removed |Added Status|NEW |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33435
[Bug fortran/36515] Integer read from stdin yields a value overflow for a valid integer.
--- Comment #13 from jvdelisle at gcc dot gnu dot org 2008-06-16 16:29 --- Keep this opened until I update the documentation files. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36515
[Bug fortran/36276] [4.3/4.4 Regression] possible issue with opening fortran files?
--- Comment #7 from burnus at gcc dot gnu dot org 2008-06-16 17:54 ---
Better patch. I'm not sure whether we are ever freeing the memory, but I think
even if not, it is not a big problem.
Index: scanner.c
===
--- scanner.c (Revision 136838)
+++ scanner.c
@@ -1654,7 +1654,8 @@ preprocessor_line (gfc_char_t *c)
if (strcmp (current_file->filename, filename) != 0)
{
- gfc_free (current_file->filename);
+ /* The current_file->filename may not be freed here as it still needs to
+be accessible by lookup_line. */
current_file->filename = gfc_getmem (strlen (filename) + 1);
strcpy (current_file->filename, filename);
}
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36276
[Bug fortran/36342] [4.4 Regression] Missing file name in compilation diagnostics of preprocessed fortran source
--- Comment #8 from burnus at gcc dot gnu dot org 2008-06-16 17:56 --- Mark as waiting. Can any of you try whether the bug still exists for you? -- burnus at gcc dot gnu dot org changed: What|Removed |Added Status|NEW |WAITING http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36342
[Bug fortran/36132] _gfortran_internal_pack on optional arguments
--- Comment #8 from burnus at gcc dot gnu dot org 2008-06-16 18:08 --- Pointer for myself (or someone else): Should be added in trans-array.c's gfc_conv_array_parameter and maybe also gfc_trans_dummy_array_bias. -- burnus at gcc dot gnu dot org changed: What|Removed |Added CC||burnus at gcc dot gnu dot ||org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36132
[Bug c++/35022] [4.3/4.4 regression] ICE with parameter pack in template constant parameter
--- Comment #5 from chris dot fairles at gmail dot com 2008-06-16 19:34
---
I think this is related:
template struct A{};
template class B> struct C{};
int main() { C a; }
gives ICE @ pt.c:15861 (rev 136843).
The line in question is:
gcc_assert (TREE_CODE (type) != TEMPLATE_TYPE_PARM);
in
bool dependant_type_p (tree type);
--
chris dot fairles at gmail dot com changed:
What|Removed |Added
CC||chris dot fairles at gmail
||dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35022
[Bug other/25757] Small memory leak in 'prefix_from_string' of file 'collect2.c'
--- Comment #3 from christophe dot jaillet at wanadoo dot fr 2008-06-16 19:50 --- This has been fixed in revision 124532 on Sun Jul 15 11:45:30 2007 UTC. (http://gcc.gnu.org/viewcvs/trunk/gcc/collect2.c?r1=124532&r2=126653&diff_format=h) -- christophe dot jaillet at wanadoo dot fr changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25757
[Bug fortran/36342] [4.4 Regression] Missing file name in compilation diagnostics of preprocessed fortran source
--- Comment #9 from pault at gcc dot gnu dot org 2008-06-16 20:22 --- (In reply to comment #8) > Mark as waiting. Can any of you try whether the bug still exists for you? > This works for me - x86_ia64/Fedora8 - gcc version 4.4.0 20080615 Taking a risk, given Tobias' report - marking as fixed. Paul -- pault at gcc dot gnu dot org changed: What|Removed |Added Status|WAITING |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36342
[Bug fortran/36342] [4.4 Regression] Missing file name in compilation diagnostics of preprocessed fortran source
--- Comment #10 from dfranke at gcc dot gnu dot org 2008-06-16 21:49 --- Reopened. I can still observe the problem with trunk from 20080615 (r136827). $> gfortran-svn -O -Wall ~/pr/pr36342.F90 ž: In function 'test': hqë·š:4: warning: 'junk_2' is used uninitialized in this function In addition, the invalid reads are still shown by valgrind. FX, could you have a look which part of your patch (r134992, one of the wide-char patches I think) might have introduced the problem? -- dfranke at gcc dot gnu dot org changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36342
[Bug testsuite/36544] fseek.f90 does not correctly account for newline lengths
--- Comment #1 from jvdelisle at gcc dot gnu dot org 2008-06-17 01:05 --- Subject: Bug 36544 Author: jvdelisle Date: Tue Jun 17 01:05:11 2008 New Revision: 136856 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136856 Log: 2008-06-16 Jerry DeLisle <[EMAIL PROTECTED]> PR fortran/36544 * gfortran.dg/fseek.f90: Adjust test conditions for variable newline. Modified: trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gfortran.dg/fseek.f90 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36544
[Bug testsuite/36544] fseek.f90 does not correctly account for newline lengths
--- Comment #2 from jvdelisle at gcc dot gnu dot org 2008-06-17 01:08 --- Revised test case passes on win64. -- jvdelisle at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36544
[Bug c/36548] New: likely integer codegen bug
At -O and higher with -fwrapv, svn 136854 improperly compiles func_9 below into
object code returning 0.
static unsigned long
mod_rhs (long int rhs)
{
return rhs;
}
unsigned g_8 = 0x0815898FL;
int func_9 (void)
{
return ((0x0274952FL * g_8) % mod_rhs (0x0274952FL));
}
--
Summary: likely integer codegen bug
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: regehr at cs dot utah dot edu
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36548
[Bug libfortran/36546] Namelist error with tab following a comma and newline
--- Comment #3 from jvdelisle at gcc dot gnu dot org 2008-06-17 04:14 --- Subject: Bug 36546 Author: jvdelisle Date: Tue Jun 17 04:14:07 2008 New Revision: 136859 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136859 Log: 2008-06-16 Jerry DeLisle <[EMAIL PROTECTED]> PR fortran/36546 * io/list_read.c (eat_separator): Add tab character to condition for looping past whitespace. Modified: trunk/libgfortran/ChangeLog trunk/libgfortran/io/list_read.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36546
[Bug libfortran/36546] Namelist error with tab following a comma and newline
--- Comment #4 from jvdelisle at gcc dot gnu dot org 2008-06-17 04:18 --- Subject: Bug 36546 Author: jvdelisle Date: Tue Jun 17 04:18:11 2008 New Revision: 136860 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=136860 Log: 2008-06-16 Jerry DeLisle <[EMAIL PROTECTED]> PR fortran/36546 * gfortran.dg: namelist_49.f90: New test. Added: trunk/gcc/testsuite/gfortran.dg/namelist_49.f90 Modified: trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36546
[Bug libfortran/36546] Namelist error with tab following a comma and newline
--- Comment #5 from jvdelisle at gcc dot gnu dot org 2008-06-17 04:32 --- I will backport this to 4.3 in a few days. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36546
[Bug c++/36549] New: offsetof defined as function in contravention of ISO/IEC 14882:1998 17.4.1.2 para 5
>Class: rejects-legal
>Release: gcc (GCC) 4.2.3
>Description:
like bug 14932 - 4.2.3 c++ does not allow variable array index in macro
offsetof
it looks like offsetof maps to a builtin function:
#define offsetof(TYPE, MEMBER) __builtin_offsetof (TYPE, MEMBER)
This appears to be in contravention of ISO/IEC 14882:1998 17.4.1.2 para 5:
"Names which are defined as macros in C shall be defined as macros in the C++
Standard Library, even if C grants license for implementation as functions.
[Note: the names defined as macros in C include the following: assert, errno,
offsetof, setjump, va_arg, va_end and va_start. -end note]"
>How-To-Repeat:
#include
struct A {
int array[10];
};
std::size_t off(int x) { return offsetof(struct A, array[x]); }
$ g++ offsetof.cc -S
offsetof.cc: In function 'size_t off(int)':
offsetof.cc:7: error: 'x' cannot appear in a constant-expression
$ cat offsetof.s
.file "offsetof.cc"
>Fix:
use a macro (as mandated for c++) - e.g. /usr/include/iso/stddef_iso.h:
#define offsetof(s, m) (std::size_t)(&(((s *)0)->m))
--
Summary: offsetof defined as function in contravention of ISO/IEC
14882:1998 17.4.1.2 para 5
Product: gcc
Version: 4.2.3
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: ajrobb at bigfoot dot com
GCC build triplet: i386-pc-solaris2.10
GCC host triplet: i386-pc-solaris2.10
GCC target triplet: i386-pc-solaris2.10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36549
