http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54817
Bug #: 54817
Summary: Warning about extern declarations in C and C++ files.
Classification: Unclassified
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: e
: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org
Created attachment 30497
--> http://gcc.gnu.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57884
--- Comment #1 from Eugene Zelenko ---
Created attachment 30498
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30498&action=edit
zcopy FORTRAN procedure from BLAS
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57884
--- Comment #2 from Eugene Zelenko ---
Sorry, forgot to add GCC configuration information in original report:
Using built-in specs.
COLLECT_GCC=/gcc481/bin/gcc
COLLECT_LTO_WRAPPER=/gcc481/libexec/gcc/x86_64-redhat-linux/4.8.1/lto-wrapper
Target:
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Hi!
I think will be good idea to introduce warnings for situations when non-trivial
type (of big size or with non-default copy
++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Hi!
I think will be great to have warning when void is used as function parameter
for indication of empty arguments list in C++ code (i. e. not extern "C"). Such
coding style have sen
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Hi!
I think will be great to have warning when useless semicolon trails closing
curly bracket (closing function definition or code block). Same should be done
for C.
Eugene.
: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Target Milestone: ---
Created attachment 44454
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44454&action=edit
Problematic code snippet
I experienced ICE in build_base_path
: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Target Milestone: ---
I had crash in optimized build because pointer check is skipped in next
situation (null pointer is sneaked into container):
void setData( Data &
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71069
--- Comment #1 from Eugene Zelenko ---
Sorry for mistake in original report. -Waddress should report such problems.
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Target Milestone: ---
-Wterminate description is missing in "Options to Request or Suppress
Warnings".
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Target Milestone: ---
Created attachment 38579
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38579&action=edit
Simp
IRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Target Milestone: ---
-Wuseless-cast doesn't detect casting string literals to (const char*), like
(const char*) "strin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59793
--- Comment #2 from Eugene Zelenko ---
Something like that:
class Class
{
private:
int Data;
public:
int GetData() const;
};
int Class::GetData() const {
return Data;
}
erity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Target Milestone: ---
[GCC 5, 6, 7] -Wuseless-cast doesn't detect unnecessary removal of const.
For example:
static void Function(
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82790
--- Comment #2 from Eugene Zelenko ---
Just a little bit of background: a lot of legacy C code was converted to C++,
so a lot of type casts were necessary to compile it properly. Gradually char *
are converted to const char *, so -Wuseless-cast w
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Hi!
I think will be great to have warning which will suggest to make non-vuirtual
method const if doesn't modify object's state and/or call only other const
methods.
Eugene.
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Hi!
I think will be great to have warning which will suggest to make trivial
non-vuirtual method inline and move to class declaration. Possible criteria of
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59570
Eugene Zelenko changed:
What|Removed |Added
Keywords||diagnostic
--- Comment #1 from Eugene Ze
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64431
Eugene Zelenko changed:
What|Removed |Added
CC||eugene.zelenko at gmail dot com
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Will be good idea to -Wmissing-declarations to variables. Global variable
should have extern declaration in header file, otherwise variable should be
static.
Clang detect such situations with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60407
Eugene Zelenko changed:
What|Removed |Added
CC||eugene.zelenko at gmail dot com
ty: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene.zelenko at gmail dot com
Target Milestone: ---
It looks like there is no way to disable this warning (at least in 5.2.0).
Part of my code base is built with -Werror, so I usu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66918
--- Comment #2 from Eugene Zelenko ---
(In reply to Andrew Pinski from comment #1)
> Could you explain why you don't want to have this warning really. This
> warning is telling you that the inline function is not defined just like
> static func
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66918
--- Comment #4 from Eugene Zelenko ---
(In reply to Manuel López-Ibáñez from comment #3)
> Does Clang have an option for this? GCC could use the same name.
>
> (The same warning exists in the C++ FE, thus it should be controlled by the
> same op
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71069
--- Comment #3 from Eugene Zelenko ---
(In reply to Andrew Pinski from comment #2)
> -fsantize=undefined will catch this at runtime. What is undefined is
> passing a NULL to setData.
It'll be much better to report such problems during compilati
26 matches
Mail list logo
