On Thu, Mar 7, 2019 at 7:20 PM Martin Sebor wrote:
>
> On 3/4/19 6:17 AM, Richard Biener wrote:
> > On Mon, Mar 4, 2019 at 1:23 PM Jakub Jelinek wrote:
> >>
> >> On Mon, Mar 04, 2019 at 01:13:29PM +0100, Richard Biener wrote:
> >* Make TREE_NO_WARNING more fine-grained
> > (inspi
On Fri, Mar 8, 2019 at 8:56 AM Vanida Plamondon
wrote:
>
> I have been working on some PPA's that will provide standard Ubuntu
> and Linux Mint packages that are compiled with the znver1 cpu
> optimisations (Ryzen CPU). It has been quite tedious (though not
> particularly hard) to modify existing
I realise that, however, debian packages seem to use multiple build
systems (automake, dh_automake, ninja, etc.), and have no standard
(that is adhered to), for setting up each build environment.
Additionally, some packages seem to throw their build configuration
setup throughout multiple files tha
I've written up my GCC 9 work in blog form here:
https://developers.redhat.com/blog/2019/03/08/usability-improvements-in-gcc-9/
I'm working on a patch for changes.html, to cover the same material.
(sorry about the shameless self-promotion)
Dave
On Fri, 8 Mar 2019 at 11:28, Vanida Plamondon
wrote:
>
> I realise that, however, debian packages seem to use multiple build
> systems (automake, dh_automake, ninja, etc.), and have no standard
> (that is adhered to), for setting up each build environment.
> Additionally, some packages seem to thr
OK, so it seems I need to give more information to clarify what I am
trying to do.
I am not invoking or configuring gcc directly. I am creating debian
source code packages which are then dispatched to launchpad.net, which
then automatically compiles and builds my package based on the debian
config
Hi
This may be just an ignorant user question on my part.
Can gcc report when the parameter name in a C prototype
does not match that used in the implementation?
int f(int x);
int f(int y) {...}
We try to fix every warning gcc reports but this is one that gcc
doesn't report for us. It could be
Snapshot gcc-8-20190308 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20190308/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-8
On Fri, 8 Mar 2019 at 22:00, Vanida Plamondon
wrote:
>
> OK, so it seems I need to give more information to clarify what I am
> trying to do.
>
> I am not invoking or configuring gcc directly.
(If you're creating a toolchain then surely you're configuring GCC.)
> I am creating debian
> source co
Correct. It's hard to nail down the right terminology when I'm learning by
doing. I want GCC to ignore x86 flags that aren't znver1, and keep znver1
as the default.
On Fri, Mar 8, 2019, 3:44 PM Jonathan Wakely wrote:
> On Fri, 8 Mar 2019 at 22:00, Vanida Plamondon
> wrote:
> >
> > OK, so it see
On Fri, 8 Mar 2019, Joel Sherrill wrote:
> Can gcc report when the parameter name in a C prototype
> does not match that used in the implementation?
>
> int f(int x);
>
> int f(int y) {...}
I think this would be normal and expected - an installed header would use
a reserved-namespace name for
On 09/03/2019 00:06, Joseph Myers wrote:
On Fri, 8 Mar 2019, Joel Sherrill wrote:
Can gcc report when the parameter name in a C prototype
does not match that used in the implementation?
int f(int x);
int f(int y) {...}
I think this would be normal and expected - an installed header would us
On 3/8/19, David Brown wrote:
> On 09/03/2019 00:06, Joseph Myers wrote:
>> On Fri, 8 Mar 2019, Joel Sherrill wrote:
>>
>>> Can gcc report when the parameter name in a C prototype
>>> does not match that used in the implementation?
>>>
>>> int f(int x);
>>>
>>> int f(int y) {...}
>>
>> I think thi
13 matches
Mail list logo
