[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-10-26 Thread pcarlini at suse dot de
--- Comment #10 from pcarlini at suse dot de 2007-10-26 18:58 --- *** Bug 33914 has been marked as a duplicate of this bug. *** -- pcarlini at suse dot de changed: What|Removed |Added

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-09-16 Thread pcarlini at suse dot de
--- Comment #9 from pcarlini at suse dot de 2007-09-16 22:55 --- Fixed. -- pcarlini at suse dot de changed: What|Removed |Added Status|ASSIGNED

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-09-16 Thread paolo at gcc dot gnu dot org
--- Comment #8 from paolo at gcc dot gnu dot org 2007-09-16 22:54 --- Subject: Bug 33124 Author: paolo Date: Sun Sep 16 22:54:12 2007 New Revision: 128531 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=128531 Log: /cp 2007-09-16 Paolo Carlini <[EMAIL PROTECTED]> PR c+

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-09-08 Thread gdr at cs dot tamu dot edu
--- Comment #7 from gdr at cs dot tamu dot edu 2007-09-08 20:00 --- Subject: Re: C++ frontend should not warn about new a[0] in template context "pcarlini at suse dot de" <[EMAIL PROTECTED]> writes: | Hi. So, what shall we do here? I can remove the warning completely or | conditionali

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-09-08 Thread pcarlini at suse dot de
--- Comment #6 from pcarlini at suse dot de 2007-09-08 19:09 --- Hi. So, what shall we do here? I can remove the warning completely or conditionalize it to -Wextra, for example. Just let me know... -- pcarlini at suse dot de changed: What|Removed |

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-08-20 Thread gdr at cs dot tamu dot edu
--- Comment #5 from gdr at cs dot tamu dot edu 2007-08-21 00:19 --- Subject: Re: C++ frontend should not warn about new a[0] in template context "ian at airs dot com" <[EMAIL PROTECTED]> writes: | The problem I see is that this unconditional warning warns about code which is | complet

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-08-20 Thread ian at airs dot com
--- Comment #4 from ian at airs dot com 2007-08-20 23:30 --- The problem I see is that this unconditional warning warns about code which is completely safe and correct. That break -Werror builds. There is no natural way to avoid the warning in a template. Given that, if we want to hav

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-08-20 Thread gdr at cs dot tamu dot edu
--- Comment #3 from gdr at cs dot tamu dot edu 2007-08-20 23:23 --- Subject: Re: C++ frontend should not warn about new a[0] in template context "mec at google dot com" <[EMAIL PROTECTED]> writes: | "new T[0]" looks like defined behavior to me. | | [expr.new] 5.3.4 -7- | When the val

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-08-20 Thread mec at google dot com
--- Comment #2 from mec at google dot com 2007-08-20 19:31 --- "new T[0]" looks like defined behavior to me. [expr.new] 5.3.4 -7- When the value of the expression in a direct-new-declarator is zero, the allocation function is called to allocate an array with no elements. The pointer re

[Bug c++/33124] C++ frontend should not warn about new a[0] in template context

2007-08-20 Thread gdr at cs dot tamu dot edu
--- Comment #1 from gdr at cs dot tamu dot edu 2007-08-20 18:57 --- Subject: Re: New: C++ frontend should not warn about new a[0] in template context "ian at airs dot com" <[EMAIL PROTECTED]> writes: | For this simplified code: | | template | char* f1() { if (c == 0) return 0; else