Snapshot gcc-7-20180329 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20180329/
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
On Thu, Mar 29, 2018 at 8:01 PM, Mikhail Maltsev wrote:
> On Wed, Mar 28, 2018 at 11:15 PM, Katsunori Kumatani
> wrote:
>>
>> For example, I wanted to add some plugin processing (actually a top-level
>> asm statement) at the end of a translation unit (with gathered data) to add
>> some special sy
October 31
October 31, 2013
Your Payment confirmation
Dear g...@gnu.org
Thank you for paying from the Adobe Store. Here are
details about your Payment:
Adobe ID:
g...@gnu.org
On March 29, 2018 5:14:42 PM GMT+02:00, Eric Botcazou
wrote:
>> Are you suggesting we should not care about regressions with features
>> that are not enabled by default or which are only exposed with
>> "non-standard" flags? The current scheme on which bugs get P1/P2/P4+
>> assigned is quite sim
Hi,
I was wondering how much I should announce publicly about GSoC proposals
since students are not supposed to know in advance that we want any
particular one before they are officially accepted or not by google, but
I hope I will not overstep any line by saying the following:
(I am willing to i
On Wed, Mar 28, 2018 at 11:15 PM, Katsunori Kumatani <
katsunori.kumat...@gmail.com> wrote:
> For example, I wanted to add some plugin processing (actually a top-level
> asm statement) at the end of a translation unit (with gathered data) to add
> some special symbols / GAS directives (not instruc
... looking at the actually submitted proposals, I see most of the people
who contacted the mailing list have not actually submitted anything in the
end, so the selection of proposals to get slots should be straightforward
after all.
--
Joseph S. Myers
jos...@codesourcery.com
Now the student application deadline has, I understand, passed, how do we
go about collectively deciding which are the best proposals to request
slots for?
--
Joseph S. Myers
jos...@codesourcery.com
Somewhat like assembly meets c99 /javascript with maybe an extended
preprocessor macro system (#declr? )
pointers rarely contain a single value, they either reference an array, or
a group of values. In the case of the latter, the pointerVarName.FieldName
pair specifies to get the value, and then a
> Are you suggesting we should not care about regressions with features
> that are not enabled by default or which are only exposed with
> "non-standard" flags? The current scheme on which bugs get P1/P2/P4+
> assigned is quite simple...
I'm only suggesting keeping them at P3, which is not "don't
On 03/29/2018 04:15 AM, Eric Botcazou wrote:
>> I noticed there are quite many selective scheduling PRs:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84872
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84842
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84659
>>
>> and many others.
>
> Righ
> > GCC steering community I count on you and speaking behalf other
> > developers to keep GCC as close to C as possible for at least the next
> > 1000 years.
>
> We've already made a decision to use C++ when it makes sense. That ship
> sailed years ago.
I don't see "keeping GCC as close to C as
On 03/29/2018 12:56 AM, Andre Groenewald wrote:
> The heart of GCC should remain pure C as far as possible, for the very
> same reason the Linux kernel is only in C. Deviate from this, and in a
> few years we will end up with Java as the programming language of GCC.
>
> It is the duty of the steer
On Thu, Mar 29, 2018 at 12:15 PM, Eric Botcazou wrote:
>> I noticed there are quite many selective scheduling PRs:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84872
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84842
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84659
>>
>> and many others
> I noticed there are quite many selective scheduling PRs:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84872
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84842
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84659
>
> and many others.
Right, and some of them are P1/P2, which doesn't really ma
Hi,
Here's a report of a successful build and install of GCC:
$ gcc-7.3.0/config.guess
mips64el-unknown-linux-gnu
$ newcompiler/bin/gcc -v
Using built-in specs.
COLLECT_GCC=newcompiler/bin/gcc
COLLECT_LTO_WRAPPER=/home/aaro/gcctest/newcompiler/libexec/gcc/mipsel-unknown-linux-gnu/7.3.0/lto-wrapp
16 matches
Mail list logo