Re: Possible Bug Fix/No Reply on Bugzilla

2017-09-28 Thread Manuel López-Ibáñez

On 27/09/17 21:56, nick wrote:

Greetings All,

I commented here a few names ago, 
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82230. Not
to be a annoyance but I have a school assignment and would like someone to 
reply if it's
correct or something. I am assuming it's probably wrong but any comment would 
be very
helpful before I sent in a patch to the patches list to get merged for the fix.

Take care,
Nick


Dear Nick,

Long time ago, I was in your position as a newbie volunteer contributor. Please 
let me share some suggestions that I hope would help you to direct your efforts 
in the most useful and least frustrating way possible:


* Nobody can reply to all comments in bugzilla, there are just too many.

* People contributing to GCC are already very busy with their own projects, 
bugs, priorities. Unfortunately, there is very little time left for mentoring, 
in particular of sporadic contributors: You are more likely to get a reply if 
you are a frequent contributor. You have to be very self-motivated, because the 
start will be slow (I have more tips to share about how to overcome this phase 
if you are interested).


* People may not know the answer to what you are asking or it may require 
investing a significant amount of time to find out the answer, thus they reply 
nothing.


* People are not likely to spend time testing a fix that is "probably wrong". 
They would hope that you make the effort to test it yourself.


How to move your fix forward? My suggestion would be: Check that it works. 
Check out trunk, apply your fix, create a testcase, run the testsuite and check 
that it fixes the issue and it doesn't break anything else.


More detailed instructions: 
https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps


I'd also suggest to read: https://gcc.gnu.org/wiki/Community

Happy hacking!

Manuel.


gcc-7-20170928 is now available

2017-09-28 Thread gccadmin
Snapshot gcc-7-20170928 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/7-20170928/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7-branch 
revision 253270

You'll find:

 gcc-7-20170928.tar.xzComplete GCC

  SHA256=90cab3643cd1359283a1f966eb710ae1be8050bad5427d148f500ce27a19cf92
  SHA1=0095beda6e51a835760467b314f2ff1181a46520

Diffs from 7-20170921 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-7
link is updated and a message is sent to the gcc list.  Please do not use
a snapshot before it has been announced that way.


Re: Possible Bug Fix/No Reply on Bugzilla

2017-09-28 Thread R0b0t1
Sir,

On Thu, Sep 28, 2017 at 4:03 PM, Manuel López-Ibáñez
 wrote:
> On 27/09/17 21:56, nick wrote:
>>
>> Greetings All,
>>
>> I commented here a few names ago,
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82230. Not
>> to be a annoyance but I have a school assignment and would like someone to
>> reply if it's
>> correct or something. I am assuming it's probably wrong but any comment
>> would be very
>> helpful before I sent in a patch to the patches list to get merged for the
>> fix.
>>
>> Take care,
>> Nick
>
>
> Dear Nick,
>
> Long time ago, I was in your position as a newbie volunteer contributor.
> Please let me share some suggestions that I hope would help you to direct
> your efforts in the most useful and least frustrating way possible:
>
> * Nobody can reply to all comments in bugzilla, there are just too many.
>
> * People contributing to GCC are already very busy with their own projects,
> bugs, priorities. Unfortunately, there is very little time left for
> mentoring, in particular of sporadic contributors: You are more likely to
> get a reply if you are a frequent contributor. You have to be very
> self-motivated, because the start will be slow (I have more tips to share
> about how to overcome this phase if you are interested).
>

I would very much appreciate this information.

A number of years ago, now, I started trying to do something very
simple. Now I am here, because this is the most direct way to
accomplish what I was trying to do. When I type most questions I have
into Google I get no results, and when I ask them I receive no
responses.

I can not remember what I was originally trying to do.

Respectfully,
 R0b0t1