confirm subscribe to gcc-help@gcc.gnu.org

confirm subscribe to gcc-help@gcc.gnu.org

[shonnagunti]

Re: confirm subscribe to gcc-help@gcc.gnu.org

[Jonathan Wakely]

You're replying to the wrong addresses.

On 28 October 2017 at 08:08, Yubin Ruan <yubinr@fastmail.com> wrote:
>
>
> On Sat, Oct 28, 2017, at 12:06 AM, gcc-help-help@gcc.gnu.org wrote:
>> Hi! This is the ezmlm program. I'm managing the
>> gcc-help@gcc.gnu.org mailing list.
>>
>> To confirm that you would like
>>
>>    yubinr@fastmail.com
>>
>> added to the gcc-help mailing list, please send
>> an empty reply to this address:
>>
>>    gcc-help-sc.1509174391.appknpopdfaolmoiinaf-yubinr=fastmail.com@gcc.gnu.org
>>
>> Usually, this happens when you just hit the "reply" button.
>> If this does not work, simply copy the address and paste it into
>> the "To:" field of a new message.
>>
>> This confirmation serves two purposes. First, it verifies that I am able
>> to get mail through to you. Second, it protects you in case someone
>> forges a subscription request in your name.
>>
>> Some mail programs are broken and cannot handle long addresses. If you
>> cannot reply to this request, instead send a message to
>> <gcc-help-request@gcc.gnu.org> and put the
>> entire address listed above into the "Subject:" line.
>>
>>
>> --- Administrative commands for the gcc-help list ---
>>
>> I can handle administrative requests automatically. Please
>> do not send them to the list address! Instead, send
>> your message to the correct command address:
>>
>> To subscribe to the list, send a message to:
>>    <gcc-help-subscribe@gcc.gnu.org>
>>
>> To remove your address from the list, send a message to:
>>    <gcc-help-unsubscribe@gcc.gnu.org>
>>
>> Send mail to the following for info and FAQ for this list:
>>    <gcc-help-info@gcc.gnu.org>
>>    <gcc-help-faq@gcc.gnu.org>
>>
>> Similar addresses exist for the digest list:
>>    <gcc-help-digest-subscribe@gcc.gnu.org>
>>    <gcc-help-digest-unsubscribe@gcc.gnu.org>
>>
>> To get messages 123 through 145 (a maximum of 100 per request), mail:
>>    <gcc-help-get.123_145@gcc.gnu.org>
>>
>> To get an index with subject and author for messages 123-456 , mail:
>>    <gcc-help-index.123_456@gcc.gnu.org>
>>
>> They are always returned as sets of 100, max 2000 per request,
>> so you'll actually get 100-499.
>>
>> To receive all messages with the same subject as message 12345,
>> send an empty message to:
>>    <gcc-help-thread.12345@gcc.gnu.org>
>>
>> The messages do not really need to be empty, but I will ignore
>> their content. Only the ADDRESS you send to is important.
>>
>> You can start a subscription for an alternate address,
>> for example "john@host.domain", just add a hyphen and your
>> address (with '=' instead of '@') after the command word:
>> <gcc-help-subscribe-john=host.domain@gcc.gnu.org>
>>
>> To stop subscription for this address, mail:
>> <gcc-help-unsubscribe-john=host.domain@gcc.gnu.org>
>>
>> In both cases, I'll send a confirmation message to that address. When
>> you receive it, simply reply to it to complete your subscription.
>>
>> If despite following these instructions, you do not get the
>> desired results, please contact my owner at
>> gcc-help-owner@gcc.gnu.org. Please be patient, my owner is a
>> lot slower than I am ;-)
>>
>> --- Enclosed is a copy of the request I received.
>>
>> Return-Path: <anonymous@sourceware.org>
>> Received: (qmail 4558 invoked by uid 48); 28 Oct 2017 07:06:30 -0000
>> Message-ID: <20171028070630.4555.qmail@sourceware.org>
>> From: anonymous@sourceware.org
>> Date: Sat, 28 Oct 2017 07:06:30 +0000
>> To: gcc-help-subscribe-yubinr=fastmail.com@sourceware.org
>> User-Agent: Heirloom mailx 12.4 7/29/08
>> MIME-Version: 1.0
>> Content-Type: text/plain; charset=us-ascii
>> Content-Transfer-Encoding: 7bit
>>
>>

Re: confirm subscribe to gcc-help@gcc.gnu.org

[Yubin Ruan]

On Sat, Oct 28, 2017, at 12:06 AM, gcc-help-help@gcc.gnu.org wrote:
> Hi! This is the ezmlm program. I'm managing the
> gcc-help@gcc.gnu.org mailing list.
> 
> To confirm that you would like
> 
>    yubinr@fastmail.com
> 
> added to the gcc-help mailing list, please send
> an empty reply to this address:
> 
>    gcc-help-sc.1509174391.appknpopdfaolmoiinaf-yubinr=fastmail.com@gcc.gnu.org
> 
> Usually, this happens when you just hit the "reply" button.
> If this does not work, simply copy the address and paste it into
> the "To:" field of a new message.
> 
> This confirmation serves two purposes. First, it verifies that I am able
> to get mail through to you. Second, it protects you in case someone
> forges a subscription request in your name.
> 
> Some mail programs are broken and cannot handle long addresses. If you
> cannot reply to this request, instead send a message to
> <gcc-help-request@gcc.gnu.org> and put the
> entire address listed above into the "Subject:" line.
> 
> 
> --- Administrative commands for the gcc-help list ---
> 
> I can handle administrative requests automatically. Please
> do not send them to the list address! Instead, send
> your message to the correct command address:
> 
> To subscribe to the list, send a message to:
>    <gcc-help-subscribe@gcc.gnu.org>
> 
> To remove your address from the list, send a message to:
>    <gcc-help-unsubscribe@gcc.gnu.org>
> 
> Send mail to the following for info and FAQ for this list:
>    <gcc-help-info@gcc.gnu.org>
>    <gcc-help-faq@gcc.gnu.org>
> 
> Similar addresses exist for the digest list:
>    <gcc-help-digest-subscribe@gcc.gnu.org>
>    <gcc-help-digest-unsubscribe@gcc.gnu.org>
> 
> To get messages 123 through 145 (a maximum of 100 per request), mail:
>    <gcc-help-get.123_145@gcc.gnu.org>
> 
> To get an index with subject and author for messages 123-456 , mail:
>    <gcc-help-index.123_456@gcc.gnu.org>
> 
> They are always returned as sets of 100, max 2000 per request,
> so you'll actually get 100-499.
> 
> To receive all messages with the same subject as message 12345,
> send an empty message to:
>    <gcc-help-thread.12345@gcc.gnu.org>
> 
> The messages do not really need to be empty, but I will ignore
> their content. Only the ADDRESS you send to is important.
> 
> You can start a subscription for an alternate address,
> for example "john@host.domain", just add a hyphen and your
> address (with '=' instead of '@') after the command word:
> <gcc-help-subscribe-john=host.domain@gcc.gnu.org>
> 
> To stop subscription for this address, mail:
> <gcc-help-unsubscribe-john=host.domain@gcc.gnu.org>
> 
> In both cases, I'll send a confirmation message to that address. When
> you receive it, simply reply to it to complete your subscription.
> 
> If despite following these instructions, you do not get the
> desired results, please contact my owner at
> gcc-help-owner@gcc.gnu.org. Please be patient, my owner is a
> lot slower than I am ;-)
> 
> --- Enclosed is a copy of the request I received.
> 
> Return-Path: <anonymous@sourceware.org>
> Received: (qmail 4558 invoked by uid 48); 28 Oct 2017 07:06:30 -0000
> Message-ID: <20171028070630.4555.qmail@sourceware.org>
> From: anonymous@sourceware.org
> Date: Sat, 28 Oct 2017 07:06:30 +0000
> To: gcc-help-subscribe-yubinr=fastmail.com@sourceware.org
> User-Agent: Heirloom mailx 12.4 7/29/08
> MIME-Version: 1.0
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> 

RE: confirm subscribe to gcc-help@gcc.gnu.org

[Rob Curtis]

Hi Folks, 
We are cross-compiling for the Hitachi H8 micro for a little embedded
project.

Much of the source code functions are never called and I expected the
compiler to optimise these functions away but reading through through
some of the output I get references to functions that never get called
(and have no pointers to them). 
I'm no expert at gcc. Can someone tell me what output I should be
looking at to see how the optimisation has gone?
Our little embedded micro is full and I need to write still more code.

The compile options (sucked out of our make file) are:

CFLAGS=-g -m$(ARCH) -O2 -fsigned-char -pedantic -malign-300 -fno-common
-fshort-enums -Wall

I thought the -g flag was to add debugger code but it doesn't seem to
make any difference.
It seems that constant strings are the culprit. I removed some and the
build is OK, and I can add up to a certain size without it blowing up.
Reduce the size of the string by a few bytes and still put in a 200
instruction function and it still survives. P.S. the huge string that
causes it to blow up is in a function that has no reference to its
address (and so I thought it should be removed).

Any help would be much appreciated.

Regards,

Rob Curtis
   ___________________
|=/__________________/=|=====()>
Norseld Laser & Control P/L

Re: confirm subscribe to gcc-help@gcc.gnu.org

[Koliya N Pulasinghe]