On 6/13/19 10:46 AM, Tom Tromey wrote:
>> "Jeff" == Jeff Law writes:
>
> Jeff> I'd like to move C-alloca support to the ash heap of history. But I'm
> Jeff> not sure we can realistically do that.
>
> Are there still platforms or compilers in use where it's needed?
>
> For gdb I was plannin
Snapshot gcc-7-20190613 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20190613/
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, 13 Jun 2019, Martin Jambor wrote:
> architecture supports it. (and if IIUC, the intent is to use the 0 mode
> from table 4-8 in
> https://software.intel.com/sites/default/files/managed/39/c5/325462-sdm-vol-1-2abcd-3abcd.pdf
> in instructions that take a rounding a mode to implement rounde
On 6/13/19 10:46 AM, Tom Tromey wrote:
"Jeff" == Jeff Law writes:
Jeff> I'd like to move C-alloca support to the ash heap of history. But I'm
Jeff> not sure we can realistically do that.
Are there still platforms or compilers in use where it's needed?
For gdb I was planning to just remove t
On Thu, Jun 13, 2019 at 10:39 AM Joel Sherrill wrote:
> Ok with me if no one steps up and the downstream projects like Debian gets
> notice. This is just a reflection of this architecture's status in the
> world.
I sent email to the debian-ia64 list half an hour ago. Just got a
response. They m
Ok with me if no one steps up and the downstream projects like Debian gets
notice. This is just a reflection of this architecture's status in the
world.
--joel
On Thu, Jun 13, 2019, 4:13 AM Richard Biener wrote:
>
> ia64 has no maintainer anymore so the following deprecates it
> with the goal o
On Thu, 2019-06-13 at 09:09 -0600, Jeff Law wrote:
> On 6/13/19 5:13 AM, Richard Biener wrote:
> >
> > ia64 has no maintainer anymore so the following deprecates it
> > with the goal of eliminating the port for GCC 11 if no maintainer
> > steps up.
OK with me since I'm not the maintainer anymore.
Hi Tejas,
On Thu, Jun 13 2019, Tejas Joshi wrote:
> Hello.
> As further part of implementing roundeven is inlining, I was studying
> machine descriptions and I have a few questions.
>
> As suggested, builtin functions provided a strong model for
> implementing roundeven. Keeping that in mind, I tr
Hi Tejas,
On Wed, Jun 12 2019, Tejas Joshi wrote:
> Hello.
> Is this the correct sequence for regression test:
> 1. Revert back all the changes I made and then configure, build along with
> make bootstrap
> make -k check
> collect the *.sum files
> 2. Apply the patch and do the configuration, buil
> "Jeff" == Jeff Law writes:
Jeff> I'd like to move C-alloca support to the ash heap of history. But I'm
Jeff> not sure we can realistically do that.
Are there still platforms or compilers in use where it's needed?
For gdb I was planning to just remove these calls.
Tom
On Thu, Jun 13, 2019 at 03:59:33PM +, Michael Matz wrote:
> without running the risk of unlimited stack use. But of course this would
> promote a programming style that'd only work with our alloca (and not even
> C-alloca), and we want to avoid that. I thought it a cute idea, but was
> car
Hi,
On Thu, 13 Jun 2019, Jeff Law wrote:
> > (In fact I think our builtin_alloca implementation could benefit when we
> > added that behaviour as well; it's a natural wish to be able to free
> > memory that you allocated).
>
> Also note that simply sprinkling alloca(0) calls won't magically re
On 6/12/19 10:40 AM, Jakub Jelinek wrote:
> On Wed, Jun 12, 2019 at 10:13:57AM -0600, Martin Sebor wrote:
>> But GCC doesn't support such an implementation, does it?
>
> Why would that be relevant? The warning would cause people to make portable
> code less portable (by removing the alloca (0) ca
On 6/12/19 9:25 AM, Michael Matz wrote:
> Hi,
>
> On Wed, 12 Jun 2019, Martin Sebor wrote:
>
>>> Otherwise LGTM as the patch, but I'd like to hear from others whether
>>> it is kosher to add such a special case to the warn_unused_result
>>> attribute warning. And if the agreement is yes, I thi
On 6/13/19 5:13 AM, Richard Biener wrote:
>
> ia64 has no maintainer anymore so the following deprecates it
> with the goal of eliminating the port for GCC 11 if no maintainer
> steps up.
>
> OK?
>
> Thanks,
> Richard.
>
> 2019-06-13 Richard Biener
>
> * config.gcc: Mark ia64*-*-* tar
Hello.
As further part of implementing roundeven is inlining, I was studying
machine descriptions and I have a few questions.
As suggested, builtin functions provided a strong model for
implementing roundeven. Keeping that in mind, I tried to inspect how
similar functions (round/ceil) would get in
ia64 has no maintainer anymore so the following deprecates it
with the goal of eliminating the port for GCC 11 if no maintainer
steps up.
OK?
Thanks,
Richard.
2019-06-13 Richard Biener
* config.gcc: Mark ia64*-*-* targets as deprecated/obsolete.
Index: gcc/config.gcc
=
On Wed, Jun 12, 2019 at 10:17 PM wrote:
>
> When doing a build, we use a pipe between GCC and GAS.
> And because we wish to do some analysis of the assembly code,
> we do not use -pipe but instead do '-S -c -'. And this has worked
> fine for many years.
Can you please show us complete command-li
18 matches
Mail list logo
