Hi, community!
To simplify generating a preprocessed file if ICE is occurred, GCC
(since 5.0 version) introduces a special -freport-bug option. Looking to
GCC bug reporting guide (https://gcc.gnu.org/bugs/#detailed), it may be
useful to mention -freport-bug on this page. Does this make sense?
On 20/01/16 10:08, Sriraman Tallam wrote:
On Fri, Jan 15, 2016 at 9:51 AM, Yury Gribov wrote:
On 01/15/2016 08:44 PM, vivek pandya wrote:
Thanks Yury for
https://gcc.gnu.org/ml/gcc-patches/2011-09/msg01440.html this link.
It implements procedure reordering as linker plugin.
I have some quest
Hi.
On 31/03/16 12:52, Gayan Pathirage wrote:
Hi,
I find it difficult to locate the information regarding the version of
the sanitizers (i.e. LLVM Sanitizers) integrated with GCC 4.9.3. Could
anyone suggest me a location where I can find this information.
This is indeed difficult. AFAIK, ther
?
AFAIK, there aren't any plans on porting MSan and DFSan to GCC (see
https://gcc.gnu.org/ml/gcc/2014-10/msg0.html for MSan). TSan and
UBSan are already present in GCC.
-Maxim
Best Regards,
Gayan
On Thu, Mar 31, 2016 at 4:40 PM, Maxim Ostapenko
wrote:
Hi.
On 31/03/16 12:52,
Hi!
Although in languages like C and C++ unsigned integer overflow reliably
wraps around and well defined, sometimes it may indicate an error in
code and lead to undesirable consequences and even security
vulnerabilities
(https://android-developers.blogspot.ru/2016/05/hardening-media-stack.ht
CC'ing Jakub, Marek and Kostya, sanitizer maintainers in GCC.
On 04/07/16 14:12, Maxim Ostapenko wrote:
Hi!
Although in languages like C and C++ unsigned integer overflow
reliably wraps around and well defined, sometimes it may indicate an
error in code and lead to undesirable consequ
On 11/07/16 18:05, Jakub Jelinek wrote:
On Tue, Jul 05, 2016 at 10:31:31AM +0300, Maxim Ostapenko wrote:
CC'ing Jakub, Marek and Kostya, sanitizer maintainers in GCC.
Jakub, thanks for your summary.
I'm not convinced it is a good idea, that is why we've intentionally left it
On 11/07/16 19:28, Jeff Law wrote:
On 07/11/2016 10:08 AM, Maxim Ostapenko wrote:
On 11/07/16 18:05, Jakub Jelinek wrote:
On Tue, Jul 05, 2016 at 10:31:31AM +0300, Maxim Ostapenko wrote:
CC'ing Jakub, Marek and Kostya, sanitizer maintainers in GCC.
Jakub, thanks for your summary.
I&
On 12/07/16 12:20, Yuri Gribov wrote:
On Tue, Jul 12, 2016 at 9:48 AM, Maxim Ostapenko
wrote:
On 11/07/16 19:28, Jeff Law wrote:
On 07/11/2016 10:08 AM, Maxim Ostapenko wrote:
On 11/07/16 18:05, Jakub Jelinek wrote:
On Tue, Jul 05, 2016 at 10:31:31AM +0300, Maxim Ostapenko wrote:
CC
Hi,
On 21/10/16 16:46, Jakub Jelinek wrote:
Status
==
Trunk which will eventually become GCC 7 is still in Stage 1 but its
end is near and we are planning to transition into Stage 3 starting
Nov 13th end of day time zone of your choice.
This means it is time to get things you want to have
On 25/10/16 11:36, Jakub Jelinek wrote:
On Tue, Oct 25, 2016 at 11:32:25AM +0300, Maxim Ostapenko wrote:
On 21/10/16 16:46, Jakub Jelinek wrote:
Status
==
Trunk which will eventually become GCC 7 is still in Stage 1 but its
end is near and we are planning to transition into Stage 3
Hi,
At this moment, most of GCC builtin memory functions (for example
strcpy, stpcpy, wcpcpy, strdup, etc) are not instrumented by GCC,
however some of them are rather dangerous. If GCC inlines these builtin
functions, we will miss important checks for arguments, and possible
overflow won't b
Hi,
On 23/01/17 14:33, Jakub Jelinek wrote:
Hi!
I've noticed today there is tsan_rtl_ppc64.S file since the latest
merge from upstream. Does that mean tsan is supposed to work
on ppc64? Just powerpc64le-*-linux*, or powerpc64-*-linux* too?
FWIW LLVM has build bots for both ppc64le-linux and
13 matches
Mail list logo
