I would really like to see the Severity field removed from the bug
entry form. A few people use it correctly to mark their bugs as
enhancements or trivial, but most users just set it to "blocker"
because they think it means "how important is this to you?". Obviously
everyone's bug is important to t
On Tue, Dec 8, 2015 at 1:04 PM, Jonathan Wakely wrote:
> I would really like to see the Severity field removed from the bug
> entry form. A few people use it correctly to mark their bugs as
> enhancements or trivial, but most users just set it to "blocker"
> because they think it means "how import
On 8 December 2015 at 12:42, Richard Biener wrote:
> On Tue, Dec 8, 2015 at 1:04 PM, Jonathan Wakely wrote:
>> I would really like to see the Severity field removed from the bug
>> entry form. A few people use it correctly to mark their bugs as
>> enhancements or trivial, but most users just set
On 8 December 2015 at 13:16, Jonathan Wakely wrote:
> On 8 December 2015 at 12:42, Richard Biener
> wrote:
>> People also get Component wrong but it would be inconvenient
>> to have it dropped. Maybe have an advanced bug reporting form
>> and a simple one?
>
> We already have a "Hide advanced f
Richard Biener wrote on 12/03/2015 03:32 PM:
On Thu, Dec 3, 2015 at 8:54 AM, Uday P. Khedker wrote:
We are implementing points-to analysis in GCC 4.7.2 and need to distinguish
between
pointers to scalars and the pointers to structures. This distinction by
using the TYPE (TREE_TYPE)
hierarchy
Jonathan Wakely writes:
> We already have a "Hide advanced fields" toggle, maybe we should just
> flip the default setting for that.
They are already hidden by default (the last choice is remembered in a
cookie).
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196
On Tue, Dec 8, 2015 at 3:35 PM, Richard Biener
wrote:
> On Tue, Dec 8, 2015 at 3:22 PM, Uday P. Khedker wrote:
>>
>>
>> Richard Biener wrote on 12/03/2015 03:32 PM:
>>>
>>> On Thu, Dec 3, 2015 at 8:54 AM, Uday P. Khedker
>>> wrote:
We are implementing points-to analysis in GCC 4.7.2 an
On Tue, Dec 8, 2015 at 3:22 PM, Uday P. Khedker wrote:
>
>
> Richard Biener wrote on 12/03/2015 03:32 PM:
>>
>> On Thu, Dec 3, 2015 at 8:54 AM, Uday P. Khedker
>> wrote:
>>>
>>> We are implementing points-to analysis in GCC 4.7.2 and need to
>>> distinguish
>>> between
>>> pointers to scalars and
Le 08. 12. 15 14:16, Jonathan Wakely a écrit :
>> Dropping it is ok I think.
>
> Yes, even for the valid "enhancement" cases a maintainer who triages
> the report could set that easily enough.
If maintainers still use the severity field to triage bugs, then it
should not be dropped. It would be m
On 12/8/2015 4:26 PM, Frédéric Buclin wrote:
> Le 08. 12. 15 14:16, Jonathan Wakely a écrit :
>>> Dropping it is ok I think.
>>
>> Yes, even for the valid "enhancement" cases a maintainer who triages
>> the report could set that easily enough.
>
> If maintainers still use the severity field to tri
Good Afternoon,
My colleagues and I are doing a study on compilers. We have some questions
related to gcc and the compilation process that we were hoping you could help
us with.
In a general sense, we were wondering what optimizations may be occurring in
the front-end stages of the compiler?
On 12/08/2015 12:32 PM, Jodi A. Miller wrote:
Good Afternoon,
My colleagues and I are doing a study on compilers. We have some
questions related to gcc and the compilation process that we were
hoping you could help us with.
In a general sense, we were wondering what optimizations may be
occurr
On Tue, 8 Dec 2015, Jodi A. Miller wrote:
One algebraic simplification we are seeing is particularly interesting.
Given the following code snippet intended to check for buffer overflow,
which is actually undefined behavior in C++, we expected to maybe see
the if check optimized away entirely.
Snapshot gcc-5-20151208 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/5-20151208/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 5 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-5
14 matches
Mail list logo
