Re: gcc rodata regression

2015-02-01 Thread Andreas Schwab
Simon Glass  writes:

> According to the bug report this does not happen on x86_64,

That is not true, see comment #6.

Andreas.

-- 
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


Re: Rename C files to .c in GCC source

2015-02-01 Thread Eli Zaretskii
> From: DJ Delorie 
> Cc: gcc@gcc.gnu.org, Jonny Grant 
> Date: Fri, 30 Jan 2015 16:39:51 -0500
> 
> However, we should avoid relying on case-sensitive file systems
> (Windows) and use .cc or .cxx for C++ files ("+" is not a valid file
> name character on Windows, so we can't use .c++).

Actually, Windows filesystems do allow '+' in file names.  (DOS
filesystems don't.)

But I agree that using it is not the best alternative, as the Windows
shell sometimes interprets '+' as a delimiter, so file names using
that character need to be quoted for safety.


Re: Rename C files to .c in GCC source

2015-02-01 Thread Eli Zaretskii
> Date: Sat, 31 Jan 2015 01:55:29 +
> From: Jonathan Wakely 
> Cc: Andrew Pinski , "gcc@gcc.gnu.org" , 
> Jonny Grant 
> 
> These files are only compiled by GCC's own build system, with GCC's
> own makefiles, so we know we invoke the C++ compiler and so the
> language isn't inferred from the file extension, and so we aren't
> relying on case-sensitive file systems.

That is true for building GCC.  But what about editors and other
development tools?  They _will_ be affected.


Re: Rename C files to .c in GCC source

2015-02-01 Thread Kevin Ingwersen (Ingwie Phoenix)

> Am 01.02.2015 um 17:09 schrieb Eli Zaretskii :
> 
>> Date: Sat, 31 Jan 2015 01:55:29 +
>> From: Jonathan Wakely 
>> Cc: Andrew Pinski , "gcc@gcc.gnu.org" , 
>> Jonny Grant 
>> 
>> These files are only compiled by GCC's own build system, with GCC's
>> own makefiles, so we know we invoke the C++ compiler and so the
>> language isn't inferred from the file extension, and so we aren't
>> relying on case-sensitive file systems.
> 
> That is true for building GCC.  But what about editors and other
> development tools?  They _will_ be affected.

Indeed. Atom keeps thinking .C is an actual „ANSI C“ thing. If I were to make a 
suggestion to the GCC dev’s, then I probably could also swiftly word it as:

$ find gcc-src -name "*.C“ | while read f; do mv $f $(echo $f | sed 
's/\.C/\.cxx/g’); done

In other words; .cxx, .cpp or .cc seems like a solution that works across 
platforms. Since .cc is already used at some places, I would recommend that 
this is to be the extension to choose.

One does not neccessarily need to make a dev apply hacks all over just to start 
development.

gcc-5-20150201 is now available

2015-02-01 Thread gccadmin
Snapshot gcc-5-20150201 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/5-20150201/
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/trunk revision 220336

You'll find:

 gcc-5-20150201.tar.bz2   Complete GCC

  MD5=3b78baaf124e3aad875eaf318b31989e
  SHA1=0558cb236c982b5e1931ed18fc06967b3da1cd99

Diffs from 5-20150125 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-5
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: gcc rodata regression

2015-02-01 Thread Simon Glass
 Hi Andreas,

On 1 February 2015 at 01:55, Andreas Schwab  wrote:
> Simon Glass  writes:
>
>> According to the bug report this does not happen on x86_64,
>
> That is not true, see comment #6.

OK, so it is a widespread problem then. Do you have any hints on how I
could begin to figure out how to fix this? It is blocking me from
making progress so I'm willing to invest some time.

Regards,
Simon


"Call for Papers for the 2015 National Indigenous Conferences"

2015-02-01 Thread Indigenous Conference Services
"Call for Papers for the 2015 National Indigenous Conferences"
Inspired by the hugely successful staging of last year’s Indigenous Conferences 
in Cairns, the event organizers are now calling for papers for the five 
exciting events being launched this month with the  closing date of submitting 
paper on February 28, 2015. 
The 2015 Indigenous Men’s and Indigenous Women’s Conferences will be held in 
Darwin on the 12th – 14th of September. 
Similarly, papers are also being called for the Indigenous Board of Directors 
Conference scheduled for the 19th – 21st of October 
 2015 National Indigenous Domestic Violence Conference to be held on 28th – 
30th of October respectively. Both October events will be held at the Mercure 
Gold Coast Resort.
Furthermore, the 2015 National Indigenous Health Conference will be held in 
Cairns and scheduled for the 1st – 3rd December, 2015.

Guidelines in Submitting Paper:
Papers should not contain offensive language and take into account 
cultural sensitivities of host Aboriginal country.
Papers may treat the themes in a manner that contributes to further 
discussion of conference aims.
Conference papers must be presented in the finish format not less than 
60 days prior to the event.
First round of papers closing date will be on February 28, 2015. Papers 
that are not chosen in the first round may be resubmitted in the second round.
Papers should be submitted in Microsoft Word format.
Authors of papers presented at the conference will be formally notified 
of their acceptance.
Registration fee of $650 will apply to all persons submitting papers 
payable upon acceptance of papers.
Papers should explore ways in which the themes show up in the 
philosophy of the conference.
All papers must be presented in a positive and informative light.

For more information, please visit the conference website at 
www.indigenousconferences.com or  contact us by email at admin...@iinet.net.au
TO UNSUBSCRIBE – PLEASE CLICK REPLY AND WRITE ‘STOP’ ON SUBJECT LINE.