Priority: P3
Component: driver
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schwab at linux-m68k dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45703
--- Comment #2 from schwab at linux-m68k dot org 2010-08-22 08:16 ---
Assigning -1 to an unsigned type is always safe.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45372
--- Comment #2 from schwab at linux-m68k dot org 2010-08-20 15:35 ---
There is a lot of normal valid C we warn about...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45358
--- Comment #1 from schwab at linux-m68k dot org 2010-08-18 08:19 ---
That's how it is defined by the respective ABIs. On i386-linux a struct field
has at most 32-bit alignment. Add explicit padding or compile with
-malign-double if you want to be compatible to the mingw32 ABI
--- Comment #2 from schwab at linux-m68k dot org 2010-08-14 08:44 ---
Your operator is not strict (!operator(x,x) for all x).
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #5 from schwab at linux-m68k dot org 2010-08-12 15:24 ---
ISO/IEC 9899:1999, 6.9.1 Function definitions
9. Each parameter has automatic storage duration. Its identifier is an lvalue,
which is in effect declared at the head of the compound statement that
constitutes
--- Comment #9 from schwab at linux-m68k dot org 2010-08-12 15:52 ---
The parameters contain copies of the argument values (6.9.1#10: as if by
assignment). The address of a parameter has no meaning.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45265
--- Comment #2 from schwab at linux-m68k dot org 2010-08-11 17:30 ---
Obviously the compiler is not working. That needs config.log to tell anything.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45084
--- Comment #5 from schwab at linux-m68k dot org 2010-08-10 12:42 ---
The most portable way to put a pointer value in a jlong is a = (uintptr_t)arg.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45246
--- Comment #1 from schwab at linux-m68k dot org 2010-08-04 16:40 ---
*** This bug has been marked as a duplicate of 33547 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #2 from schwab at linux-m68k dot org 2010-08-04 16:40 ---
*** Bug 45184 has been marked as a duplicate of this bug. ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #3 from schwab at linux-m68k dot org 2010-07-29 12:21 ---
That does not change the fact that vus*vus can be assumed to be non-negative.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #5 from schwab at linux-m68k dot org 2010-07-29 12:55 ---
Works fine here with gcc 4.4.4.
movzwl vus, %eax
movzwl vus, %edx
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #5 from schwab at linux-m68k dot org 2010-07-28 12:26 ---
Calling a function with a different signature than declared is undefined in any
case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45106
--- Comment #6 from schwab at linux-m68k dot org 2010-07-22 12:59 ---
Huh? This is one byte, how does endianess come into play?
By the use of bitfields.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45017
--- Comment #2 from schwab at linux-m68k dot org 2010-07-02 20:27 ---
Fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Status|UNCONFIRMED
--- Comment #4 from schwab at linux-m68k dot org 2010-06-16 09:06 ---
If the variable is not modified between setjmp and longjmp the compiler is
required to preserve its value.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #1 from schwab at linux-m68k dot org 2010-06-16 09:35 ---
The first operand of - must be a valid pointer to an object.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #4 from schwab at linux-m68k dot org 2010-06-16 10:53 ---
Undefined behaviour.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #4 from schwab at linux-m68k dot org 2010-06-10 10:12 ---
You need to use the %U and %X modifiers together with m. If the insn does
not support them (no update and/or indexed form) you cannot use m. Basically
this means you can use m only with the normal load/store insns
--- Comment #6 from schwab at linux-m68k dot org 2010-06-10 10:59 ---
You can use them as many times as needed.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492
--- Comment #7 from schwab at linux-m68k dot org 2010-06-10 11:06 ---
A matched constraint can never have side effects, and the powerpc specific uses
are already correct (though they could take advantage of the es or Z
constraints).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
--- Comment #9 from schwab at linux-m68k dot org 2010-06-10 11:50 ---
You cannot use an m operand more than once, since it can include side
effects.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492
--- Comment #13 from schwab at linux-m68k dot org 2010-06-10 12:39 ---
m is defined to be the most general memory constraint, and a pre/post
modified memory operand is still a memory operand.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492
--- Comment #14 from schwab at linux-m68k dot org 2010-06-10 12:42 ---
asm (... %2 ... : =m (*p) : m (*p), r (p));
In this case the compiler should never use a side effect.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492
--- Comment #15 from schwab at linux-m68k dot org 2010-06-10 12:46 ---
The %X modifier has nothing to do with side effects, it is used for indexed
addressing modes.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492
--- Comment #18 from schwab at linux-m68k dot org 2010-06-10 15:09 ---
One option is to add a sequence point before every asm statement.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492
--- Comment #19 from schwab at linux-m68k dot org 2010-06-10 15:19 ---
Of course, there _is_ already a sequence point before every statement. Doh.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44492
--- Comment #1 from schwab at linux-m68k dot org 2010-06-07 11:19 ---
You are getting eof.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #4 from schwab at linux-m68k dot org 2010-05-24 15:48 ---
*** This bug has been marked as a duplicate of 21920 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #152 from schwab at linux-m68k dot org 2010-05-24 15:48 ---
*** Bug 44260 has been marked as a duplicate of this bug. ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Keywords: wrong-code
Severity: normal
Priority: P3
Component: middle-end
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schwab at linux-m68k dot org
GCC target triplet: powerpc*-*-*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44151
--- Comment #2 from schwab at linux-m68k dot org 2010-05-15 20:35 ---
*** This bug has been marked as a duplicate of 44103 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #4 from schwab at linux-m68k dot org 2010-05-15 20:35 ---
*** Bug 44151 has been marked as a duplicate of this bug. ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #1 from schwab at linux-m68k dot org 2010-05-10 14:43 ---
Try -Wstrict-aliasing.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #15 from schwab at linux-m68k dot org 2010-05-03 20:17 ---
The patch is ok, please check it in.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43804
--- Comment #1 from schwab at linux-m68k dot org 2010-05-03 20:26 ---
This isn't really a different bug.
*** This bug has been marked as a duplicate of 42909 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #3 from schwab at linux-m68k dot org 2010-05-03 20:26 ---
*** Bug 42910 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42909
--- Comment #1 from schwab at linux-m68k dot org 2010-04-29 12:09 ---
A throw-expression cannot be part of a integral constant expression, thus it
cannot be a null pointer constant.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #9 from schwab at linux-m68k dot org 2010-04-22 09:20 ---
Probably the author of T didn't realise that !-mpcrel in (!-mpcrel 's') is
already implied. It is already a no-op in the -mpcrel case.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43804
--- Comment #4 from schwab at linux-m68k dot org 2010-04-21 13:22 ---
Introduced in r27576. Presumably the first alternative is supposed to catch
this case, through T+g, but T does not match if flag_pic, contrary to its
documentation (introduced in r120961).
--
http://gcc.gnu.org
--- Comment #6 from schwab at linux-m68k dot org 2010-04-21 22:51 ---
(In reply to comment #5)
assuming -mpcrel and -fpic are equivalent:
They aren't. -mpcrel implies -fpic, but not the other way round.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43804
--- Comment #7 from schwab at linux-m68k dot org 2010-04-21 23:40 ---
I think 'T' should accept tls references like 's' does.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43804
--- Comment #2 from schwab at linux-m68k dot org 2010-04-19 13:28 ---
An array cannot have internal padding, so the padding needs to be added to the
element type.
The attempt to define such an array should probably be rejected.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43798
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schwab at linux-m68k dot org
GCC target triplet: m68k
--- Comment #1 from schwab at linux-m68k dot org 2010-04-19 20:13 ---
Created an attachment (id=20424)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20424action=view)
Preprocessed testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43804
--- Comment #2 from schwab at linux-m68k dot org 2010-04-19 20:14 ---
Created an attachment (id=20425)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20425action=view)
Reduced testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43804
--- Comment #4 from schwab at linux-m68k dot org 2010-04-17 09:49 ---
The compiler can assume that *x is correctly aligned, so this is not a bug.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #2 from schwab at linux-m68k dot org 2010-04-08 09:45 ---
configured by ../gcc/configure, generated by GNU Autoconf 2.64,
with options '--prefix=/usr' '--build=x86_64-linux' '--enable-shared'
'--enable-threads=posix' '--with-system-zlib' '--enable-__cxa_atexit
--- Comment #4 from schwab at linux-m68k dot org 2010-04-08 11:04 ---
Sorry, I had a broken experimental change that I forgot to remove.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
: 4.5.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code, build
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schwab at linux-m68k dot org
GCC target triplet: x86_64
--- Comment #6 from schwab at linux-m68k dot org 2010-04-07 16:15 ---
MOVEA always sign extends.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43675
--- Comment #5 from schwab at linux-m68k dot org 2010-04-05 09:36 ---
m68k-*-coff is no longer supported.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #2 from schwab at linux-m68k dot org 2010-04-03 09:16 ---
ยง6.4.4.1 Integer constants:
If an integer constant cannot be represented by any type in its list, it may
have an extended integer type, if the extended integer type can represent its
value. If all of the types
--- Comment #5 from schwab at linux-m68k dot org 2010-04-01 15:59 ---
You have a bad c++ in your path:
configure:4892: checking whether we are using the GNU C++ compiler
configure:4911: c++ -c conftest.cpp 5
/usr/local/libexec/gcc/i686-pc-cygwin/4.5.0/cc1plus.exe: error while loading
--- Comment #6 from schwab at linux-m68k dot org 2010-04-01 16:05 ---
AC_PROG_CXX was added with the --enable-build-with-cxx support.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43619
--- Comment #3 from schwab at linux-m68k dot org 2010-03-09 21:59 ---
Fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Status|UNCONFIRMED
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schwab at linux-m68k dot org
GCC target triplet: m68k-*-*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43294
--- Comment #1 from schwab at linux-m68k dot org 2010-03-07 22:07 ---
9223372036854775807 has more significant bits than what fits in a double, it is
rounded to 9223372036854775808.0, which then overflows when converted to long
long.
--
schwab at linux-m68k dot org changed
--- Comment #3 from schwab at linux-m68k dot org 2010-02-07 09:15 ---
Use -Werror-implicit-function-declaration.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #2 from schwab at linux-m68k dot org 2010-01-25 19:44 ---
m68k-unknown-amigaos is not a valid target.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Severity|blocker |normal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42754
--- Comment #13 from schwab at linux-m68k dot org 2010-01-17 22:27 ---
The bug exists since the dawn of time. The problem is that cse thinks that
(zero_extract:SI (mem:QI ...) ...) is zero if (mem:QI ...) is known to be zero,
but the first argument of zero_extract is only a base
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Known to fail||4.3.4 4.4.3
Target Milestone|--- |4.4.4
--- Comment #2 from schwab at linux-m68k dot org 2010-01-12 16:24 ---
*** This bug has been marked as a duplicate of 11751 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #86 from schwab at linux-m68k dot org 2010-01-12 16:24 ---
*** Bug 42711 has been marked as a duplicate of this bug. ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #4 from schwab at linux-m68k dot org 2009-12-30 23:04 ---
Fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Status|NEW
--- Comment #7 from schwab at linux-m68k dot org 2009-12-29 11:58 ---
Please report that to the provider of your inofficial builds. Neither
m68k-amigaos nor m68k-atari-mint are supported by the official sources.
--
schwab at linux-m68k dot org changed:
What|Removed
--- Comment #10 from schwab at linux-m68k dot org 2009-12-29 16:29 ---
m68k-amigaos is not a supported target.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #16 from schwab at linux-m68k dot org 2009-12-29 16:31 ---
m68k-amigaos is not a supported target.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #4 from schwab at linux-m68k dot org 2009-12-28 23:30 ---
Works for me with 4.5.0 20091228.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #1 from schwab at linux-m68k dot org 2009-12-27 17:19 ---
This is part of the rotlsi3 pattern which is disabled for coldfire since it
does not have rotate insns.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #1 from schwab at linux-m68k dot org 2009-12-05 09:14 ---
*** Bug 42297 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42296
--- Comment #1 from schwab at linux-m68k dot org 2009-12-05 09:14 ---
*** This bug has been marked as a duplicate of 42296 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #1 from schwab at linux-m68k dot org 2009-11-25 12:39 ---
sprintf(mystring,%s world,mystring);
Overlapping copies are undefined.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #2 from schwab at linux-m68k dot org 2009-11-20 22:45 ---
Neither freeList nor serviceMsg are volatile. Thus freeList can never change
and serviceMsg = msg is a dead assignment.
--
schwab at linux-m68k dot org changed:
What|Removed
--- Comment #8 from schwab at linux-m68k dot org 2009-10-29 17:29 ---
(In reply to comment #7)
The '.*?' is the non greedy form of '.*'. If I put '.*' only, then '.*foo'
'.*' will match the foo coming after and that will not do what I want.
The nongreedy form will not prevent
--- Comment #1 from schwab at linux-m68k dot org 2009-10-22 09:32 ---
*** This bug has been marked as a duplicate of 41793 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #2 from schwab at linux-m68k dot org 2009-10-22 09:32 ---
*** Bug 41794 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41793
--- Comment #2 from schwab at linux-m68k dot org 2009-10-06 13:19 ---
This is the real problem:
/root/gcc-build/./gcc/f951: relocation error: /usr/local/lib/libmpfr.so.1:
undefined symbol: __gmp_get_memory_functions
You need to fix your libmpfr installation.
--
schwab at linux
--- Comment #2 from schwab at linux-m68k dot org 2009-09-27 15:44 ---
Fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Status|UNCONFIRMED
: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: schwab at linux-m68k dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41476
--- Comment #2 from schwab at linux-m68k dot org 2009-09-26 22:24 ---
Looks like something has clobbered register A6.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41434
--- Comment #7 from schwab at linux-m68k dot org 2009-09-21 14:25 ---
(In reply to comment #3)
As far as I can see, you are triggering undefined behavior.
There is a big difference between undefined and unspecified behaviour. With
unspecified behaviour the implementation must chose
--- Comment #7 from schwab at linux-m68k dot org 2009-09-08 18:16 ---
Fix all the warnings first then try again.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
ReportedBy: schwab at linux-m68k dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41284
--- Comment #1 from schwab at linux-m68k dot org 2009-09-06 14:15 ---
Created an attachment (id=18517)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18517action=view)
Testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41284
--- Comment #3 from schwab at linux-m68k dot org 2009-09-06 14:55 ---
I don't know what m86k is, but this is obviously ppc assembler.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41284
--- Comment #11 from schwab at linux-m68k dot org 2009-09-06 16:08 ---
*** Bug 41284 has been marked as a duplicate of this bug. ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #4 from schwab at linux-m68k dot org 2009-09-06 16:08 ---
*** This bug has been marked as a duplicate of 41271 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #20 from schwab at linux-m68k dot org 2009-08-23 18:19 ---
Fixed in 4.5.0.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Status
--- Comment #13 from schwab at linux-m68k dot org 2009-08-23 18:25 ---
Fixed in 4.5.0.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Status
--- Comment #8 from schwab at linux-m68k dot org 2009-08-23 18:30 ---
No longer reproducible, assuming fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #6 from schwab at linux-m68k dot org 2009-08-23 18:34 ---
No longer reproducible, assuming fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #12 from schwab at linux-m68k dot org 2009-08-23 18:38 ---
No longer reproducible with 4.4.0, assuming fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #6 from schwab at linux-m68k dot org 2009-08-23 18:40 ---
No longer reproducible with 4.4.0, assuming fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #5 from schwab at linux-m68k dot org 2009-08-23 18:43 ---
No longer reproducible with 4.3.4, assuming fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #3 from schwab at linux-m68k dot org 2009-08-23 18:45 ---
No longer reproducible with 4.3.0, assuming fixed.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
--- Comment #12 from schwab at linux-m68k dot org 2009-08-23 18:52 ---
Wontfix for 4.3.
--
schwab at linux-m68k dot org changed:
What|Removed |Added
Status
--- Comment #1 from schwab at linux-m68k dot org 2009-06-11 13:52 ---
*** This bug has been marked as a duplicate of 40414 ***
--
schwab at linux-m68k dot org changed:
What|Removed |Added
1 - 100 of 117 matches
Mail list logo
