https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71876
--- Comment #7 from Bernd Edlinger ---
Created attachment 38915
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38915&action=edit
possible patch
This is an attempt of a fix.
Not really perfect, but should be at least safe.
Only ECF_RETURN
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Created attachment 38916
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38916&action=edit
C source code
The attached source code, when compiled with -O2 on
gcc trunk dated 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71901
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |7.0
--- Comment #1 from Andrew Pinski -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71493
--- Comment #1 from Jakub Jelinek ---
Any progress on this? We'd like to release 6.2 soon, and this is a blocker for
that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57853
--- Comment #18 from this is me ---
This is why C arrays are not pointers. It was possible to easily misconstrue
datatypes like especially with imported variables. Defined as a short integer
in one file but, is being used as a character in anothe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71107
--- Comment #5 from Bitterblue ---
Is it even possible to fix this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71795
--- Comment #4 from Thomas Koenig ---
(In reply to Vladimir Fuka from comment #3)
> I suppose it should not be P4 critical?
All Fortran regressions are classified below P3.
Fortran is not considered release critical for the
whole of gcc.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71902
Bug ID: 71902
Summary: [5/6/7 Regression] Unneeded temporary on reallocatable
character assignment
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71902
Thomas Koenig changed:
What|Removed |Added
Keywords||missed-optimization
Status|U
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71892
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71862
--- Comment #6 from Dominique d'Humieres ---
The patch for class.c in comment 2 fixes the ICE for the first test in
comment0.
The patch for resolve.c changes the error message and the tests
allocate_class_1.f90
allocate_class_2.f90
class_2.f03
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71903
Bug ID: 71903
Summary: Wrong opcode using x86 SSE _mm_cmpge_ps intrinsics
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71892
--- Comment #6 from Kern Sibbald ---
As you say, everything has been said and in any case, it is clear that you are
going to stick with the current compiler behavior. What you have failed to
understand is that I do very well understand that certa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71795
Thomas Koenig changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71795
--- Comment #6 from Vladimir Fuka ---
(In reply to Thomas Koenig from comment #4)
> (In reply to Vladimir Fuka from comment #3)
> > I suppose it should not be P4 critical?
>
> All Fortran regressions are classified below P3.
> Fortran is not con
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71904
Bug ID: 71904
Summary: comparing this to NULL should give a warning by
default (this == NULL)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhanc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71892
--- Comment #7 from Manuel López-Ibáñez ---
(In reply to Kern Sibbald from comment #6)
> As you say, everything has been said and in any case, it is clear that you
> are going to stick with the current compiler behavior. What you have failed
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71899
--- Comment #1 from Daniel Krügler ---
I have now a working implementation available, my minimum requirement set is
summarized by the following trait definition:
//
// Utility to detect BooleanTestable types (NB
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71795
--- Comment #7 from Thomas Koenig ---
(In reply to Vladimir Fuka from comment #6)
> Agree, but it is currently P4 critical.
P1 is most important (release blocker), P2 is important
(no more than 100 at release), P3 is unclassified, P4
and P5 are
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71463
--- Comment #6 from Martin Sebor ---
I didn't know that GCC considers attribute warn_unused_result part of the
function type. When you say that most of these attributes apply to the
function type, which others are you referring to?
FWIW, I find
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71905
Bug ID: 71905
Summary: bogus -Wlarger-than=N and -Wframe-larger-than warnings
on small objects with large N
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310
--- Comment #12 from Jerry DeLisle ---
I have found that there is a practical limit of 2**28-1 on the size. The test
case:
program p
character, parameter :: z = 'z'
print *, repeat(z, (268435456)) ! 2**28
end
gives when compiled:
f951: o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71905
Andrew Pinski changed:
What|Removed |Added
Component|driver |middle-end
Summary|bogus -Wla
ent (if applicable):
PASS: gcc-5.3.1-2.fc23.x86_64
FAIL: gcc-6.1.1-3.fc24.x86_64
FAIL: 7.0.0 20160716 (experimental)
How reproducible:
Always.
Steps to Reproduce:
cat >stringalloc.f90 < ( character*1 )
<2>: Abbrev Number: 8 (DW_TAG_variable)
DW_AT_name: (indirect string
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66310
--- Comment #13 from Jerry DeLisle ---
(In reply to Jerry DeLisle from comment #12)
--- snip ---
>
> f951: out of memory allocating 18446744073441116160 bytes after a total of
> 569344 bytes
>
I should mention there is really nothing wrong wit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71907
Bug ID: 71907
Summary: missing buffer overflow warnings with -flto
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71907
Martin Sebor changed:
What|Removed |Added
Known to work||5.1.0
Summary|missing buffer o
=/usr/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/7.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/usr/local/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 7.0.0 20160716 (experimental) [trunk
28 matches
Mail list logo
