Re: Question regarding bug 70584

2016-05-20 Thread Daniel Gutson
On Fri, May 20, 2016 at 5:42 PM, Jeff Law wrote: > On 05/20/2016 01:18 PM, Daniel Gutson wrote: >> >> (reposting in gcc@ and adding more information) >> >> On Fri, May 20, 2016 at 3:43 PM, Andres Tiraboschi >> wrote: >>> >>> While analysing this

Re: Question regarding bug 70584

2016-05-20 Thread Daniel Gutson
(reposting in gcc@ and adding more information) On Fri, May 20, 2016 at 3:43 PM, Andres Tiraboschi wrote: > While analysing this bug we arrived to the following code at > tree.c:145 (lvalue_kind): > > case VAR_DECL: > if (TREE_READONLY (ref) && ! TREE_STATIC (ref) > && DECL_LANG_S

stray quotation marks warning enhancement or extension

2016-03-31 Thread Daniel Gutson
Hi, many times we copy code snippets from sources that change the Unicode quotation marks ( “ ” ) rather than " ". For example const std::string a_string(“Hello”); That line looks innocent but causes gcc to say x.cpp:4:1: error: stray ‘\342’ in program const std::string a_string

Re: avoiding recursive calls of calloc due to optimization

2015-09-21 Thread Daniel Gutson
On Mon, Sep 21, 2015 at 2:26 PM, Andrew Pinski wrote: > On Mon, Sep 21, 2015 at 10:20 AM, Daniel Gutson > wrote: >> This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html >> >> Currently, gcc provides an optimization that transforms a call to >&g

Re: avoiding recursive calls of calloc due to optimization

2015-09-21 Thread Daniel Gutson
On Mon, Sep 21, 2015 at 3:33 PM, Daniel Gutson wrote: > On Mon, Sep 21, 2015 at 2:26 PM, Andrew Pinski wrote: >> On Mon, Sep 21, 2015 at 10:20 AM, Daniel Gutson >> wrote: >>> This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html >>&g

avoiding recursive calls of calloc due to optimization

2015-09-21 Thread Daniel Gutson
This is derived from https://gcc.gnu.org/ml/gcc-help/2015-03/msg00091.html Currently, gcc provides an optimization that transforms a call to malloc and a call to memset into a call to calloc. This is fine except when it takes place within the calloc() function implementation itself, causing a recu

if-else-if chains to switch conversion optimization

2015-05-15 Thread Daniel Gutson
Hi, the particular motivation is a TMP compile-time search of an element, but could be extended to other scenarios. In my example, given: template struct Static_Find { static size_t find(size_t /*target*/) { return 0; } }; template struct Static_Find { static size_t

Re: Re: Obscure crashes due to gcc 4.9 -O2 => -fisolate-erroneous-paths-dereference

2015-02-19 Thread Daniel Gutson
(Hi Sandra, so long!) On Thu, Feb 19, 2015 at 5:56 PM, Sandra Loosemore wrote: > Jakub Jelinek wrote: >> >> >> On Wed, Feb 18, 2015 at 11:21:56AM -0800, Jeff Prothero wrote: >>> >>> Starting with gcc 4.9, -O2 implicitly invokes >>> >>> -fisolate-erroneous-paths-dereference: >>> >>> which >>>

Re: Possible LRA issue?

2014-08-27 Thread Daniel Gutson
From: gcc-ow...@gcc.gnu.org [mailto:gcc-ow...@gcc.gnu.org] On Behalf Of > Daniel Gutson > Sent: Wednesday, August 27, 2014 7:58 PM > To: gcc Mailing List > Subject: Possible LRA issue? > > Hi, > >I have a large codebase where at some point, there's a structure that

Possible LRA issue?

2014-08-27 Thread Daniel Gutson
Hi, I have a large codebase where at some point, there's a structure that takes an unsigned integer template argument, and uses as the size of an array, something like template struct Struct { typedef std::array Chunk; typedef std::list Content; Content c; }; Changing the values

Possible "C++ for embedded systems" WG21 working group

2014-08-21 Thread Daniel Gutson
Hi falks, since the last WG21 meeting held at Rapperswil, where I gave a presentation of issues and opportunities to improve in the C++ language regarding embedded systems development, I'm pursuing the creation of a Committee's Working Group. There was agreement that the issues were relevant a

dynamic_cast of a reference and -fno-exceptions

2014-05-19 Thread Daniel Gutson
Hi, should gcc warn at least if a dynamic_cast of a reference is used when -fno-exceptions is specified? At least 4.8.2 doesn't complain. If so, I can implement the fix. Example: struct Base { virtual void f(){} }; struct Der : Base {}; int main() { Der d; Base& b = d; dyna

Re: True "no-exceptions" mode?

2014-05-18 Thread Daniel Gutson
On Sun, May 18, 2014 at 4:42 PM, Basile Starynkevitch wrote: > On Sun, 2014-05-18 at 12:33 -0300, Daniel Gutson wrote: >> Hi, >> >>I am needing a truly exceptions-clean (or exceptions-free) binary due to >> some embedding systems platform. >> -fno-exceptions i

Re: True "no-exceptions" mode?

2014-05-18 Thread Daniel Gutson
On Sun, May 18, 2014 at 1:12 PM, Jonathan Wakely wrote: > >> Comments? > > Sounds like a coding standard not a compiler multilib target. > > If you don't want exceptions don't use them. If the STL is compiled with exceptions support, I can't get rid off its overhead. It's not just about not using

True "no-exceptions" mode?

2014-05-18 Thread Daniel Gutson
Hi, I am needing a truly exceptions-clean (or exceptions-free) binary due to some embedding systems platform. -fno-exceptions is not enough of course. I am thinking about taking the concept to the backend through multilibs: add some general -mno-exceptions or alike so there can be a selectable

Re: implementation question

2014-05-09 Thread Daniel Gutson
On Mon, May 5, 2014 at 8:57 AM, Richard Biener wrote: > On Mon, May 5, 2014 at 11:28 AM, Andrew Haley wrote: >> On 05/05/2014 08:47 AM, Richard Biener wrote: >>> It really depends on how "3x" should materialize in the end. >>> How do you triplicate ops with side-effects? If you only >>> triplica

implementation question

2014-04-30 Thread Daniel Gutson
Hi, assuming the need to generate code in which almost everything is used 3x (e.g. 3x registers, 3 times data, etc.) for a specific purpose (*) for any given target, what would be the best way to implement it? (let's name this 3ple-voting behavior) a) as a forked backend target of each target

Re: SPARC LEON3 and CAS instruction

2014-04-25 Thread Daniel Gutson
On Fri, Apr 25, 2014 at 1:31 PM, Eric Botcazou wrote: >> recent GCC versions support the C11 atomic operations for the SPARC LEON3 >> processor via the CASA instruction. GCC emits CASA instructions with an ASI >> of 0x80. I think this is due to the usage of "cas" if I get the stuff in >> sync.md

4.8.3?

2014-04-03 Thread Daniel Gutson
Hi, is there any plan to release a gcc 4.8.3? Thanks, Daniel. -- Daniel F. Gutson Chief Engineering Officer, SPD San Lorenzo 47, 3rd Floor, Office 5 Córdoba, Argentina Phone: +54 351 4217888 / +54 351 4218211 Skype: dgutson

Re: [PATCH] pedantic warning behavior when casting void* to ptr-to-func, 4.8 and 4.9

2014-04-01 Thread Daniel Gutson
On Tue, Apr 1, 2014 at 3:52 PM, Jonathan Wakely wrote: > On 1 April 2014 15:00, Daniel Gutson wrote: >>> For regressions, yes, but I don't think this is a regression. >> >> Why not? (I don't know the criteria, please let me know). > > Did it work in p

Re: [PATCH] pedantic warning behavior when casting void* to ptr-to-func, 4.8 and 4.9

2014-04-01 Thread Daniel Gutson
On Tue, Apr 1, 2014 at 10:54 AM, Jonathan Wakely wrote: > On 1 April 2014 14:43, Daniel Gutson wrote: >> >> The attached patch attempts to fix this issue. Since I no longer have >> write access, please >> apply this for me if correct (is the 4.8 branch still alive for

[PATCH] pedantic warning behavior when casting void* to ptr-to-func, 4.8 and 4.9

2014-04-01 Thread Daniel Gutson
ven specifying -std=c++03. Please let me know if this is truly a bug, in which case I could also fix it for the latest version as well (if so, please let me know if I should look into trunk or any other branch). Thanks, Daniel. 2014-03-31 Daniel Gutson gcc/cp/ * typeck.c (build_reinter

Re: question regarding new warning

2014-03-27 Thread Daniel Gutson
On Thu, Mar 27, 2014 at 6:48 AM, Manuel López-Ibáñez wrote: > On 27/03/14 09:52, Florian Weimer wrote:> On 03/27/2014 08:44 AM, > Andrew Haley wrote: >> >>> On 03/26/2014 03:05 PM, Daniel Gutson wrote: >>> >>>> assigning a negative literal to

question regarding new warning

2014-03-26 Thread Daniel Gutson
Hi, assigning a negative literal to an unsigned variable issues no warning: unsigned int x; x =- 4; This is specially important in typos when -= was intended instead of =- Would be acceptable if I add a new warning to handle this, i.e. -Wnegative-to-unsigned or alike? Thanks,