https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
Bug ID: 79868
Summary: aarch64: diagnostic "malformed target %s value" not
translateable
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #1 from Roland Illig ---
Same for:
error ("target %s %qs is invalid", pragma_or_attr, token);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #2 from Roland Illig ---
Also, the word "attribute" appeared as an untranslated literal:
ret = aarch64_process_target_attr (args, "attribute");
This makes it impossible to do any proper translation into any language other
than Engli
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78543
--- Comment #10 from Matthias Klose ---
here is one more build failure seen with 20170221, with -O1 (works with -O0),
seen in the gtk-gnutella package:
$ gcc-6 -c -O1 -msecure-plt -mcpu=power8 fileinfo.i
fileinfo.c: In function 'file_info_retrie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78543
--- Comment #11 from Matthias Klose ---
Created attachment 40883
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40883&action=edit
preprocessed source (fileinfo.i)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79869
Bug ID: 79869
Summary: i18n: document placeholders for translators
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79870
Bug ID: 79870
Summary: i18n: combine structurally identical diagnostics
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79871
Bug ID: 79871
Summary: i18n: document placeholders for translators
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78807
--- Comment #4 from Mikael Pettersson ---
On Solaris 10 / SPARC, this test case works fine when compiled by gcc-6.3.0,
but SIGBUSes when compiled by gcc-5.4.0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79872
Bug ID: 79872
Summary: document placeholder %K in gcc-internal-format
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: othe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79873
Bug ID: 79873
Summary: function_reader::handle_insn_uids: use internal_error
instead of error
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79874
Bug ID: 79874
Summary: symtab_node::verify_base: replace error with
internal_error
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Prio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79875
Bug ID: 79875
Summary: diagnostics: missing question mark after "did you
mean"
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #3 from Richard Earnshaw ---
Both pragma and attribute are keywords in the language. If the substituted
value were placed in quotes, would that help?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79868
--- Comment #4 from Roland Illig ---
(In reply to Richard Earnshaw from comment #3)
> Both pragma and attribute are keywords in the language. If the substituted
> value were placed in quotes, would that help?
No, it wouldn't. It would only conf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79876
Bug ID: 79876
Summary: [7 Regression] FAIL: libgomp.fortran/strassen.f90 -O
execution test on x86_64-apple-darwin16
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79612
--- Comment #4 from Dominique d'Humieres ---
> I cannot think of this happening with normal code. An
> internal error might be better, but internal_error does not
> take printf-style arguments.
This code has been introduced at revision r149792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68800
Bug 68800 depends on bug 79335, which changed state.
Bug 79335 Summary: [7 Regression] Conditional jump or move depends on
uninitialised in value get_scalar_to_descriptor_type(tree_node*,
symbol_attribute) (trans-expr.c:53)
https://gcc.gnu.org/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79229
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79335
vehre at gcc dot gnu.org changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70266
--- Comment #3 from paolo at gcc dot gnu.org ---
Author: paolo
Date: Sun Mar 5 17:13:16 2017
New Revision: 245901
URL: https://gcc.gnu.org/viewcvs?rev=245901&root=gcc&view=rev
Log:
/cp
2017-03-05 Paolo Carlini
PR c++/70266
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70266
Paolo Carlini changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79877
Bug ID: 79877
Summary: -Wstrict-overflow false positive or misunderstanding?
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79878
Bug ID: 79878
Summary: verify_gimple_assign_single: replace error with
internal_error
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79877
--- Comment #1 from Marc Glisse ---
The message seems pretty clear to me. gcc has an optimization that turns i-1>i
into false, and is telling you that it applied it (not that there is anything
wrong with your code). In the other code, it doesn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79871
--- Comment #1 from joseph at codesourcery dot com ---
%K means to extract a location from a statement, including inlining
context. See tree-pretty-print.c:percent_K_format. As such, the absence
of a space is correct.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79874
--- Comment #1 from joseph at codesourcery dot com ---
Without reference to whether it is the case for this particular error,
there are some cases where the code structure is:
* Make consistency checks, possibly reporting diagnostics from them.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79877
--- Comment #2 from Stephan Beyer ---
Hi,
(In reply to Marc Glisse from comment #1)
> The message seems pretty clear to me. gcc has an optimization that turns
> i-1>i into false, and is telling you that it applied it (not that there is
> anythin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
Bug ID: 79879
Summary: Integer overflow in functions from scanf() family in
MinGW, Cygwin, Borland/Embarcadero C environments
Product: gcc
Version: unknown
Status: UNCONF
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #2 from Andrew Pinski ---
Please report this to MinGW and Cygwin projects (separately). IIRC mingw has a
corrected version of scanf now. Cygwin uses newlib and not MSVCRT.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #3 from Lukas Wyporek ---
>> Cygwin uses newlib and not MSVCRT.
So why this bug is present also on Cygwin GCC?
Newlib is also buggy?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #4 from Andrew Pinski ---
(In reply to Lukas Wyporek from comment #3)
> >> Cygwin uses newlib and not MSVCRT.
>
> So why this bug is present also on Cygwin GCC?
> Newlib is also buggy?
Report it to them and find out. I don't know.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #5 from Lukas Wyporek ---
Thank you for your time.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79876
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #6 from Lukas Wyporek ---
MinGW support told me that they can do nothing because MSVCRT is closed source
library. And they told me to do direct request to GNU GCC maintainers with ask
to provide warnings in compiler when somebody is u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #7 from Andrew Pinski ---
Try with -Wall -Wextra instead of just -Wextra. IIRC -Wformat is only enabled
for -Wall and not with -Wextra.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #8 from Lukas Wyporek ---
With -Wall -Wextra instead of just -Wextra the behaviour is the same - integer
overflows.
Best regards,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #9 from Lukas Wyporek ---
No, my mistake. -Wall shows warnings only if format parameter is LITERAL.
When format parameter is pointer to string (buffer) - there are no warnings.
Best regards,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #10 from Andrew Pinski ---
(In reply to Lukas Wyporek from comment #9)
> No, my mistake. -Wall shows warnings only if format parameter is LITERAL.
> When format parameter is pointer to string (buffer) - there are no warnings.
Try -W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79871
--- Comment #2 from Roland Illig ---
Thanks for the explanation. This leaves open the %s.
Looking further in the code, I can see that %s is either the string "constant"
or the string "lane". In other diagnostics, these words are usually translat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #11 from Lukas Wyporek ---
When "%hhu" format is literal, and -Wall parameter is used there are correct
warnings - for example:
main.c:11:23: warning: unknown conversion type character 'h' in format
[-Wformat
=]
sscanf(buffer, "
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79880
Bug ID: 79880
Summary: Gcc refuses to encode vpgatherdd instruction (x86-64)
Product: gcc
Version: 7.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #12 from Andrew Pinski ---
Please read the documentation about -Wformat.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79880
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #13 from Lukas Wyporek ---
OK, so we can compile with -Wformat=2 (which can be used instead of group
"-Wformat -Wformat-nonliteral -Wformat-security -Wformat-y2k"):
gcc main.c -o main.exe -Wall -Wextra -Wformat=2
and the compiler wi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79879
--- Comment #14 from Andrew Pinski ---
(In reply to Lukas Wyporek from comment #13)
> Thank you Andrew,
> Are you Polish maybe?
Of polish decent American.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78105
PeteVine changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79881
Bug ID: 79881
Summary: -Wc++-compat should warn about sizeof character
literals
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78105
--- Comment #15 from PeteVine ---
Sorry wrong number :) I meant --enable-fix-cortex-a53-843419
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79882
Bug ID: 79882
Summary: Lack of bounds checking on -ftemplate-depth argument
Product: gcc
Version: 5.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
Bug ID: 79883
Summary: avr i18n: untranslated "interrupt" or "signal"
Product: gcc
Version: 7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: targ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
--- Comment #1 from Andrew Pinski ---
I think this is correctly untranslated as interrupt and signal here are
keywords.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79883
--- Comment #2 from Roland Illig ---
Quoting myself from bug 79868:
Although "interrupt" and "signal" are both keywords in the language, they are
not used as such in this diagnostic. Rather, they form part of the normal
sentence structure.
For
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79876
Thomas Koenig changed:
What|Removed |Added
Target Milestone|--- |7.0
--- Comment #2 from Thomas Koenig -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79884
Bug ID: 79884
Summary: Math functions with variable argument fail
Product: gcc
Version: 6.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885
Bug ID: 79885
Summary: fix-includes does not honor the value passed to
--with-build-sysroot=, looks for /usr/include instead
of looking within the SDK
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79884
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885
--- Comment #1 from Jeremy Huddleston Sequoia ---
And note that I'm not using --with-sysroot because I don't want this to affect
the compiler installed by 'make install', just what is used to build gcc
itself.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885
--- Comment #2 from Andrew Pinski ---
(In reply to Jeremy Huddleston Sequoia from comment #1)
> And note that I'm not using --with-sysroot because I don't want this to
> affect the compiler installed by 'make install', just what is used to build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78854
--- Comment #11 from Jerry DeLisle ---
Created attachment 40885
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40885&action=edit
A preliminary patch. Any and all testing greatly appreciated.
I am regression testing this now. I wanted to ge
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78854
--- Comment #12 from Jerry DeLisle ---
Here is a modified test case where I test the iotype and if its is NAMELIST, I
format the output to what would be expected. Since there is no user defined
namelist read, it just uses default reading of the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78670
--- Comment #2 from Jerry DeLisle ---
Preliminary patch given in PR78854
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885
--- Comment #3 from Jeremy Huddleston Sequoia ---
I'm not sure what you mean by using --prefix "instead" ... I'm using --prefix
to establish where I want the tools to be installed to.
As an example, if I wanted to install gcc to /opt/gcc6/bin/gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885
--- Comment #4 from Andrew Pinski ---
Try --with-build-sysroot= instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885
--- Comment #5 from Jeremy Huddleston Sequoia ---
I don't really understand what you mean by "Try --with-build-sysroot= instead."
... --with-build-sysroot= *is* being used.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79885
--- Comment #6 from Jeremy Huddleston Sequoia ---
Got farther with the Makefile.in edit and setting of CPP and CXXCPP, but
failing now because --sysroot=... is not getting passed to xg++ during
configure-stage2-gcc:
from gcc/config.log:
configu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79856
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79857
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
69 matches
Mail list logo
