On Mon, 9 Mar 2020 at 21:56, Paul Smith wrote:
> The tricky bit is that although both the host and target are always
> x86_64/i686 GNU/Linux systems, I need the generated compiler to run on
> much older systems than the one I build it on.
>
> I have a sysroot I've created (downloading RPMs from old
On Wed, 11 Mar 2020 at 16:46, Paul Smith wrote:
>
> On Wed, 2020-03-11 at 14:17 +, Jonathan Wakely wrote:
> > On Mon, 9 Mar 2020 at 21:56, Paul Smith wrote:
> > > The tricky bit is that although both the host and target are always
> > > x86_64/i686 GNU/Linux systems, I need the generated compi
On Mon, 16 Mar 2020 at 14:13, Martin Liška wrote:
>
> On 3/16/20 2:54 PM, Alexander Monakov wrote:
> > Are you trying to copy from the raw message representation?
>
> Exactly.
That's never been reliable.
On Mon, 16 Mar 2020 at 21:15, David Korczynski wrote:
>
> Hi!
>
> My name is David Korczynski and I have been doing some work on
> integrating fuzzing by way of OSS-Fuzz into the gcc project. This came
> out of fuzzing libiberty within the binutils project where we found
> several bugs within libib
On Wed, 18 Mar 2020 at 21:54, Jim Wilson wrote:
>
> I'm one of the old timers that likes our current work flow, but even I
> think that we are risking our future by staying with antiquated tools.
> One of the first things I need to teach new people is now to use email
> "properly". It is a barrier
N.B. the CC list has got too big and is causing posts to this thread
to be held for moderator approval.
On Wed, 18 Mar 2020 at 22:45, Joseph Myers wrote:
>
> On Wed, 18 Mar 2020, Jonathan Wakely via Gcc wrote:
>
> > > Some git based projects are using gerrit.
> >
> > Which I looked into previously and decided I didn't like it. If I
> > recall correctly, gerri
On Fri, 20 Mar 2020 at 07:16, jf wrote:
>
> Hi all,
>
> I'm a printf-like function lover. I always found that better than doing
> something like out << "blabla : " << var1 << ", blabla" << etc.
>
> Now, I use a lot of different platforms and to be portable, I'm supposed
> to use PRIxxx constants fo
On Sat, 21 Mar 2020 at 15:24, PRIYANSHU ARYA via Gcc wrote:
>
> Dear Sir/ma'am:
>
> I'm a new learner wanted to contribute in your open source project so i
> want to know how to start contributing in your open source projects and
> want to know all the requirements for contributing in your organiz
On Wed, 25 Mar 2020 at 04:48, Bernd Edlinger wrote:
>
> Hi,
>
> I do not want to start a flame war.
>
> I just am curious what was the reason why
> the old system cannot be used any more?
The software it ran on hasn't been maintained for years.
> Would there be a possibility to get the old look-a
On Wed, 25 Mar 2020 at 05:51, Fangrui Song wrote:
> It is really difficult for a non-subscriber to comment now.
> There are no To: or Cc: fields on Pipermail.
Yes, that's a pain. You can click on the sender's address at the top
of the archived mail (or use
https://gitlab.com/miscripts/miscripts/-/
On Wed, 25 Mar 2020 at 20:29, Bernd Edlinger wrote:
>
> -On 3/25/20 7:55 PM, Christopher Faylor wrote:
> > On Wed, Mar 25, 2020 at 04:23:02PM +0700, Arseny Solokha wrote:
> >> I believe the canonical place for the "Linux suff" mailing lists these
> >> days is
> >> lore.kernel.org, powered by publi
Please don't cross-post to both the gcc and gcc-help mailing lists.
Either your question is about GCC development, or it's about help
using GCC, not both. Pick one list.
On Thu, 26 Mar 2020 at 08:44, MAHDI LOTFI via Gcc wrote:
>
> Hello
> I am a researcher from Jam Petrochemical company I want to
On Wed, 25 Mar 2020 at 22:38, Andrew Briand wrote:
>
> Hello,
>
> I am an undergrad interested in extending GCC’s static analysis pass for GSoC
> 2020. In particular, I’m interested in adding C++ support.
>
> The selected project ideas list mentions adding new/delete checking and
> exception chec
On Wed, 1 Apr 2020 at 21:30, Bernd Edlinger wrote:
> @overseeers: PLEASE STOP IMMEDIATELY THAT SCRUBBING
You're emailing the gcc list about the gdb-patches mailing list, and
haven't CC'd the overseers list or the gdb list.
> can you act now, or do you need a CVE number first ?
That doesn't seem
On Wed, 1 Apr 2020 at 23:54, Joseph Myers wrote:
>
> On Wed, 1 Apr 2020, Bernd Edlinger wrote:
>
> > PS: I have a discovered a very serious problem with the mailing lists
> > that must be fixed by our overseers.
> >
> > That is the scubbed attachments.
> >
> > As an example please look at this one:
On Thu, 2 Apr 2020 at 04:35, Bernd Edlinger wrote:
> Regarding the overseers, they repeatedly spoke up on this list,
> but all the time they use an e-mail that bounces.
No. ONE of the overseers replies from a personal email address that
bounces, because as the address clearly says, you should cont
On Fri, 3 Apr 2020 at 18:45, Bernd Edlinger wrote:
>
> Hi,
>
> I have a question about the gcc-testresults mailing list,
> that is I see everyone using:
>
> [releases/gcc-9 revision
> 02a201f71:0f58d3b54:0e66150084aa217811a5c45fb15e98d7ed3e8839]
>
> or
>
> [master revision
> 63b2923dc6f:0c89e976d
On Fri, 3 Apr 2020 at 18:55, Bernd Edlinger wrote:
>
>
>
> On 4/3/20 7:50 PM, Jonathan Wakely wrote:
> > On Fri, 3 Apr 2020 at 18:45, Bernd Edlinger wrote:
> >>
> >> Hi,
> >>
> >> I have a question about the gcc-testresults mailing list,
> >> that is I see everyone using:
> >>
> >> [releases/gcc-9
On Fri, 3 Apr 2020 at 18:54, Bernd Edlinger wrote:
>
> On 4/3/20 7:50 PM, Jonathan Wakely wrote:
> > On Fri, 3 Apr 2020 at 18:45, Bernd Edlinger wrote:
> >>
> >> Hi,
> >>
> >> I have a question about the gcc-testresults mailing list,
> >> that is I see everyone using:
> >>
> >> [releases/gcc-9 rev
On Fri, 3 Apr 2020 at 19:40, Bernd Edlinger wrote:
>
>
>
> On 4/3/20 7:56 PM, Jonathan Wakely wrote:
> > On Fri, 3 Apr 2020 at 18:55, Bernd Edlinger
> > wrote:
> >>
> >>
> >>
> >> On 4/3/20 7:50 PM, Jonathan Wakely wrote:
> >>> On Fri, 3 Apr 2020 at 18:45, Bernd Edlinger wrote:
>
> Hi,
On Mon, 6 Apr 2020 at 23:00, Maciej W. Rozycki via Gcc wrote:
> And can certainly score a positive though not a definite rating in spam
> qualification. I don't think we ought to encourage bad IT management
> practices by trying to adapt to them too hard and hurting ourselves (our
> workflow) in
On Thu, 16 Apr 2020 at 21:02, Baumanns via Gcc wrote:
>
> Hello gcc Team,
>
> currently I work on some very modern c++ projects based on c++20. For my
> tests I would like to compile my code with all three major compilers: g++,
> msvc and llvm/clang to test the latest features (like co_yield).
> F
On Thu, 23 Apr 2020 at 06:49, Florian Weimer wrote:
>
> * Tamar Christina:
>
> > A bit late to the party, but this really doesn't work that well
> > because until recent version of gitlab there was no fairness
> > guarantee. another patch could be approved after mine (with hours
> > in between bec
On Thu, 23 Apr 2020 at 12:47, Segher Boessenkool
wrote:
>
> Hi!
>
> On Thu, Apr 23, 2020 at 12:54:04AM +, Tamar Christina wrote:
> > but trains for GCC Will likely be very short because of Changelog conflicts.
>
> Why that? Your patches should *not* touch changelog files, ever.
>
> For CI it
On Thu, 23 Apr 2020 at 16:46, Christopher Faylor via Gcc
wrote:
>
> On Thu, Apr 23, 2020 at 05:13:13PM +0200, Olivier Hainque wrote:
> >Hi Frank,
> >
> >> On 23 Apr 2020, at 16:34, Frank Ch. Eigler wrote:
> >>
> >> Hi -
> >>
> A re-subscription attempt to the gcc mailing list just
> fai
On Thu, 23 Apr 2020 at 18:02, Jonathan Wakely wrote:
>
> On Thu, 23 Apr 2020 at 16:46, Christopher Faylor via Gcc
> wrote:
> >
> > On Thu, Apr 23, 2020 at 05:13:13PM +0200, Olivier Hainque wrote:
> > >Hi Frank,
> > >
> > >> On 23 Apr 2020, at 16:34, Frank Ch. Eigler wrote:
> > >>
> > >> Hi -
> >
On Mon, 27 Apr 2020 at 04:54, Laleh Aghababaie via Gcc wrote:
>
> Hi all,
N.B. this is the wrong mailing list for such a question, you should
have used the gcc-help list instead.
> I have a question about the constexpr variable specifications and how the
> compiler handles them. The constexpr s
On Tue, 28 Apr 2020 at 02:26, luo alvin via Gcc wrote:
>
> Dear gnu:
>Here is code:
Please do not report bugs to this mailing list. Bug reports belong in
our Bugzilla database, see https://gcc.gnu.org/bugs/
But this is not a bug anyway, your code has undefined behaviour. You
cannot use m
Please move this discussion to the gcc-help mailing list where it
belongs. I'll reply on that list instead.
On Tue, 28 Apr 2020 at 07:07, luo alvin wrote:
>
> Thank you very much for replying me. I also think it not bug,because I test
> this code in the lower version(lower than 8.3.1-3) of gcc,a
On Thu, 30 Apr 2020 at 19:20, Jakub Jelinek via Gcc wrote:
>
> Status
> ==
>
> We have reached zero P1 regressions today and releases/gcc-10 branch has
> been created; GCC 10.1-rc1 will be built and announced later tonight
> or tomorrow.
> The branch is now frozen for blocking regressions and
On Tue, 5 May 2020 at 15:42, Victor Rodriguez via Gcc wrote:
> Has someone found issues on common packages that require patches for GCC 10?
Yes, several. See https://gcc.gnu.org/gcc-10/porting_to.html for the
known issues (the first one being a problem with "common" packages!)
On Thu, 7 May 2020 at 07:28, Uros Bizjak via Gcc wrote:
>
> On Thu, May 7, 2020 at 8:16 AM Richard Biener
> wrote:
> >
> > On May 6, 2020 11:15:08 PM GMT+02:00, Uros Bizjak via Gcc
> > wrote:
> > >Hello!
> > >
> > >I wonder, if the build process really needs to build all multilibs in
> > >stage
On Sat, 9 May 2020 at 08:15, John Paul Adrian Glaubitz
wrote:
>
> Hi!
>
> On 5/9/20 12:15 AM, Segher Boessenkool wrote:
> > I can do both, if you want, or just the first group? Your choice.
> >
> > But let's hear other opinions first.
>
> These bugs document the current issues with the backend as
On Sat, 9 May 2020 at 19:56, John Paul Adrian Glaubitz
wrote:
>
> On 5/9/20 12:31 PM, Arseny Solokha wrote:
> > I'd also like to nominate the following two:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52927
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60158
> >
> > which I also cannot
On Sat, 9 May 2020 at 09:56, John Paul Adrian Glaubitz
wrote:
>
> On 5/9/20 10:31 AM, Jonathan Wakely wrote:
> > If you mean for PR reasons or good apeparances, no. But it's wrong to
> > have bugs left open that only refer to unsupported versions of GCC. If
> > none of the supported releases has t
On Tue, 12 May 2020 at 09:17, Freddie Chopin wrote:
> The problem with C++ exceptions is that even in the most
> trivial of the programs and even if you don't explicitly
> use/catch/throw them, they instantly eat around 60 kB of ROM and quite
> a lot of RAM. With some hacking you can get down to ab
On Tue, 12 May 2020 at 11:48, Freddie Chopin wrote:
> To summarize. Current C++ exceptions have very huge, mostly "one-time"
> kind, cost on the size, even if not used at all by the user, mosly due
> to std::terminate() and all the string handling code inside it, as well
> as the unwind tables.
Th
On Tue, 12 May 2020, 21:57 Freddie Chopin, wrote:
>
> On Tue, 2020-05-12 at 12:07 +0100, Jonathan Wakely wrote:
> > You're talking about C++ exceptions in general, but the problems you
> > mention seems to be issues with specific implementation properties.
>
> Possibly true, but this argument - th
On Tue, 12 May 2020 at 23:39, Jonathan Wakely wrote:
> On Tue, 12 May 2020, 21:57 Freddie Chopin, wrote:
> > Anyway... If you have to recompile the toolchain, the problem is still
> > there. Most of the people (like 99,666%) will not do that for various
> > reasons. Some don't know how, some use o
On Tue, 12 May 2020, 10:15 Oleg Endo, wrote:
>
> On Tue, 2020-05-12 at 09:20 +0200, Freddie Chopin wrote:
> >
> > I actually have to build my own toolchain instead of the one provided
> > by ARM, because to really NOT use C++ exceptions, you have to recompile
> > the whole libstdc++ with `-fno-exc
On Wed, 13 May 2020 at 18:19, Mike Stump via Gcc wrote:
>
> I've changed the subject to match the 2015, 2017 and 2018 email threads.
>
> On May 13, 2020, at 3:26 AM, Thomas Schwinge wrote:
> >
> > Comparing DejaGnu/GCC testsuite '*.sum' files between two systems ("old"
> > vs. "new") that ought t
On Thu, 14 May 2020 at 07:45, Christophe Lyon wrote:
>
> On Wed, 13 May 2020 at 19:44, Jonathan Wakely via Gcc wrote:
> >
> > On Wed, 13 May 2020 at 18:19, Mike Stump via Gcc wrote:
> > >
> > > I've changed the subject to match the 2015, 2017 and 2018 e
On Mon, 18 May 2020 at 13:34, Hongyi Zhao via Gcc wrote:
>
> Hi,
>
> I want to compile qt4 on Ubuntu 20.04 which shipped with the following
> gcc version:
>
> $ gcc --version
> gcc (Ubuntu 9.3.0-10ubuntu2) 9.3.0
>
> But I'm not sure whether this gcc version is suitable for qt4. Any
> hints for th
On Tue, 19 May 2020 at 17:19, Gerald Pfeifer wrote:
>
> I hope the offer by some of you to support people like me who Git
> appears to hate with a fervor still stands? ;-)
>
> And I volunteer to enhance our documentation if it appears useful.
>
>
> Usecase: I've got a patch approved and pushed to
On Tue, 19 May 2020 at 17:36, Jonathan Wakely wrote:
>
> On Tue, 19 May 2020 at 17:19, Gerald Pfeifer wrote:
> >
> > I hope the offer by some of you to support people like me who Git
> > appears to hate with a fervor still stands? ;-)
> >
> > And I volunteer to enhance our documentation if it app
On Tue, 19 May 2020 at 17:13, Joseph Myers wrote:
>
> On Tue, 19 May 2020, Martin Liška wrote:
>
> > On 5/19/20 10:11 AM, Martin Liška wrote:
> > > Can you please share how do you do it? It would be easy to add it.
> >
> > I added the feature via --fill-up-bug-titles option. It uses common
> > requ
On Tue, 19 May 2020 at 09:26, Jakub Jelinek via Gcc wrote:
>
> On Tue, May 19, 2020 at 10:11:28AM +0200, Martin Liška wrote:
> > > I find this format more helpful for the reasons below so unless your
> > > script can be tweaked to do something similar I'd like to be able to
> > > continue to use m
On Tue, 19 May 2020 at 11:44, Martin Liška wrote:
>
> Hello.
>
> We've just installed server git hooks that verify git messages
> for a correct ChangeLog format. For a limited time period, please
> still apply ChangeLog changes to the corresponding ChangeLog files.
> We'll use it for comparison of
On Tue, 19 May 2020 at 23:19, Jonathan Wakely wrote:
>
> On Tue, 19 May 2020 at 11:44, Martin Liška wrote:
> >
> > Hello.
> >
> > We've just installed server git hooks that verify git messages
> > for a correct ChangeLog format. For a limited time period, please
> > still apply ChangeLog changes
On Wed, 20 May 2020 at 09:44, Rasmus Villemoes wrote:
>
> Hi
>
> The condition variable implementation added in commit 806dd0472f56fd
> seems to fall into the trap(s) pointed out in the paper
>
> http://birrell.org/andrew/papers/ImplementingCVs.pdf
>
> in particular, the "if no thread is current
N.B. I've redirected this to gcc-help where it's on-topic. Please
answer there instead.
On Wed, 20 May 2020 at 22:35, Ted Toth via Gcc wrote:
>
> I work on a project with a large code base some of which is pretty old. We
> are discussing adding -std=gnu++11 to our g++ compiles to be able to use
>
On Fri, 22 May 2020 at 06:54, Haoxin Tu via Gcc wrote:
>
> Hi, there!
>
> I am new for using GCC mail list, please forgive me if something is wrong.
You're using the wrong mailing list, see
https://gcc.gnu.org/lists.html which says this question should be on
the gcc-help list. Please send any rep
On Fri, 22 May 2020 at 19:15, Thomas Koenig via Gcc wrote:
>
> Hi,
>
> what's currently in trunk (as of a few hours ago) fails for me with
>
>File "contrib/mklog.py", line 36, in
> from unidiff import PatchSet
> ModuleNotFoundError: No module named 'unidiff'
>
> I think this is an error
Your question is inappropriate on this mailing list, and I already
answered it on the gcc-help list anyway.
On Thu, 28 May 2020 at 18:22, kiran kumar vangara via Gcc
wrote:
>
> Team,
>
> We have been compiling cpp files with g++ compiler on Redhat Linux OS
> machine and as part of this -mt optio
On Sat, 30 May 2020 at 21:09, Harald Anlauf wrote:
>
> Dear experts,
>
> let's assume I need to backport a series of commits on master to a release
> branch.
> In the release branch, this series of commits should become a single commit.
>
> With bare git, there is "cherry-pick -n" that seems to b
On Mon, 1 Jun 2020 at 12:56, Thomas Koenig wrote:
>
> Hi Martin,
>
> > For now, I would recommend doing 1:1 backports. Otherwise, you'll need
> > to merge
> > all ChangeLog entries in a format the server hook accepts. That can
> > require some
> > work.
>
> If the first commit caused a regression,
On Mon, 1 Jun 2020 at 13:25, Thomas Koenig wrote:
>
> Am 01.06.20 um 14:20 schrieb Jonathan Wakely via Gcc:
> > It will only "keep" it for a matter of seconds, between that
> > backported commit and the backported fix. And unless you push the
> > first commit b
On Mon, 25 May 2020 at 23:50, Jakub Jelinek via Gcc wrote:
>
> Hi!
>
> I've turned the strict mode of Martin Liška's hook changes,
> which means that from now on no commits to the trunk or release branches
> should be changing any ChangeLog files together with the other files,
> ChangeLog entry sh
On Mon, 1 Jun 2020 at 19:11, Frank Ch. Eigler via Gcc wrote:
>
> Hi -
>
> > git pull from the GCC and Glibc repos is failing for me with the error
> > below. It worked fine last week and I haven't made any changes to my
> > ssh keys.
>
> And are you logging in from the same workstation with acces
On Mon, 1 Jun 2020 at 20:16, Martin Sebor via Gcc wrote:
>
> On 6/1/20 12:10 PM, Frank Ch. Eigler wrote:
> > Hi -
> >
> >> git pull from the GCC and Glibc repos is failing for me with the error
> >> below. It worked fine last week and I haven't made any changes to my
> >> ssh keys.
> >
> > And ar
On Mon, 1 Jun 2020 at 20:46, Martin Sebor wrote:
>
> On 6/1/20 1:25 PM, Jonathan Wakely wrote:
> > On Mon, 1 Jun 2020 at 20:16, Martin Sebor via Gcc wrote:
> >>
> >> On 6/1/20 12:10 PM, Frank Ch. Eigler wrote:
> >>> Hi -
> >>>
> git pull from the GCC and Glibc repos is failing for me with th
On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote:
>
> On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
> > The libstdc++ manual is written in Docbook XML, but we commit both the
> > XML and generated HTML pages to Git. Sometimes a small XML file can
> > result
On Tue, 2 Jun 2020 at 07:44, Martin Liška wrote:
>
> On 6/1/20 7:24 PM, Jonathan Wakely wrote:
> > On Mon, 25 May 2020 at 23:50, Jakub Jelinek via Gcc wrote:
> >>
> >> Hi!
> >>
> >> I've turned the strict mode of Martin Liška's hook changes,
> >> which means that from now on no commits to the tru
On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote:
>
> On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote:
> >
> > On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
> > > The libstdc++ manual is written in Docbook XML, but we commit both the
> > >
On Tue, 2 Jun 2020 at 12:09, Jonathan Wakely wrote:
>
> On Tue, 2 Jun 2020 at 12:05, Jonathan Wakely wrote:
> >
> > On Tue, 2 Jun 2020 at 11:56, Gerald Pfeifer wrote:
> > >
> > > On Mon, 1 Jun 2020, Jonathan Wakely via Gcc-patches wrote:
> > > >
On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
>
> On 6/2/20 1:48 PM, Martin Liška wrote:
> > I tend to this approach. Let me prepare a patch candidate for it.
>
> There's a patch for it. Can you please Jonathan take a look?
Looks great, thanks!
+if name not in wildcard_prefixe
On Tue, 2 Jun 2020 at 14:56, Jonathan Wakely wrote:
>
> On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
> >
> > On 6/2/20 1:48 PM, Martin Liška wrote:
> > > I tend to this approach. Let me prepare a patch candidate for it.
> >
> > There's a patch for it. Can you please Jonathan take a look?
>
>
On Tue, 2 Jun 2020 at 21:26, Martin Sebor wrote:
>
> On 6/1/20 1:12 PM, Jonathan Wakely via Overseers wrote:
> > On Mon, 1 Jun 2020 at 19:11, Frank Ch. Eigler via Gcc
> > wrote:
> >>
> >> Hi -
> >>
> >>> git pull from the GCC and Glibc repos is failing for me with the error
> >>> below. It work
On Fri, 5 Jun 2020 at 10:12, Diego Pardo via Gcc wrote:
>
> Hi,I've installed gcc 8, how can I uninstall it?
That depends how you installed it, and you've told us nothing useful
that would allow us to help you.
But in any case, please direct this question to the
gcc-h...@gcc.gnu.org list where i
On Fri, 5 Jun 2020 at 18:59, Toon Moene wrote:
>
> On 6/5/20 6:10 PM, Tobias Burnus wrote:
>
> > On 6/5/20 4:11 PM, Jakub Jelinek via Gcc wrote:
>
> >> It is glibc that provides them, not GCC.
> >> See
> >> https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/x86/fpu/bits/math-vector.h;h=08019
On Tue, 2 Jun 2020 at 15:25, Martin Liška wrote:
>
> On 6/2/20 4:14 PM, Jonathan Wakely wrote:
> > On Tue, 2 Jun 2020 at 14:56, Jonathan Wakely wrote:
> >>
> >> On Tue, 2 Jun 2020 at 14:16, Martin Liška wrote:
> >>>
> >>> On 6/2/20 1:48 PM, Martin Liška wrote:
> I tend to this approach. Let
On Thu, 11 Jun 2020 at 08:43, MAHDI LOTFI via Gcc wrote:
>
> Hello
> I am a researcher from Jam Petrochemical company. I want to use OpenACC
> with GCC compiler(FORTRAN language). I read from your documentation that
> GCC 10.1.0 supports carrizo, fiji and vega (third and fifth generation) AMD
> GP
On Sun, 14 Jun 2020 at 22:34, Andrew Pinski via Gcc wrote:
>
> On Sun, Jun 14, 2020 at 2:27 PM Andi Kleen via Gcc wrote:
> >
> > sotrdg sotrdg via Gcc writes:
> >
> > > http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0709r0.pdf
> > >
> > > I really want this feature. How, it looks like this
On Tue, 16 Jun 2020 at 10:11, Martin Jambor wrote:
>
> Hi,
>
> On Mon, Jun 15 2020, Segher Boessenkool wrote:
> > Hi!
> >
> [...]
> > What.
> >
> > Of course it is not a fast-forward. I rebase the branches I publish,
> > what is the point of publishing them otherwise? This is so that people
> >
On Thu, 18 Jun 2020 at 19:22, Thomas Koenig via Gcc wrote:
>
> Hi,
>
> I just found a few unversioned files called .intrinsic.c.swp and
> similar in my "git status" output.
>
> Could somebody please put .*.swp into .gitignore? I'm sure this
> would save at least 10 reverts :-)
You can just add i
On Thu, 18 Jun 2020 at 20:34, Thomas Koenig wrote:
>
> Am 18.06.20 um 20:34 schrieb Jonathan Wakely via Gcc:
> > On Thu, 18 Jun 2020 at 19:22, Thomas Koenig via Gcc wrote:
> >>
> >> Hi,
> >>
> >> I just found a few unversioned files called .in
On Tue, 7 Jul 2020 at 15:41, Nino Pereira via Gcc wrote:
>
> The top line in
> https://gcc.gnu.org/onlinedocs/gcc-4.6.3/gfortran/BOZ-literal-constants.html
>
> says " The syntax is: `prefix quote digits quote', were the prefix is
> either b, o or z,"
>
> Here, 'were' must be 'where'
Thanks. That
On Fri, 10 Jul 2020 at 09:25, Unidef Defshrizzle wrote:
>
> What would happen?
This doesn't seem like a question about GCC development, so is
off-topic on this mailing list.
The C language says what should happen, GCC follows that.
Could somebody at Google please turn this crap off.
It might be confused by the change in the List-Id headers a few months
ago, but whatever the reason, please stop it.
On Thu, 23 Jul 2020 at 08:56, Google Ticket System via Gcc
wrote:
>
> You have been CC'd on a Google Ticket
On Thu, 23 Jul 2020 at 09:34, ireng ajah via Gcc wrote:
>
> Hi..
>
> Can you remove my email from your list?
No, you have to do it yourself. See
https://gcc.gnu.org/lists.html#subscribe for instructions.
On Thu, 23 Jul 2020 at 12:19, Jonathan Wakely wrote:
>
> On Thu, 23 Jul 2020 at 09:34, ireng ajah via Gcc wrote:
> >
> > Hi..
> >
> > Can you remove my email from your list?
>
> No, you have to do it yourself. See
> https://gcc.gnu.org/lists.html#subscribe for instructions.
I followed those simp
On Mon, 27 Jul 2020 at 11:59, CHIGOT, CLEMENT via Gcc wrote:
>
> Hi everyone,
>
> I'm wondering if someone knows which tar version / configuration was being
> used when creating gcc-10.2.0 tarballs ?
GNU tar 1.30, I think.
>
> I'm getting some directory checksum errors while trying to unpack it
On Mon, 27 Jul 2020 at 12:34, Jonathan Wakely wrote:
>
> On Mon, 27 Jul 2020 at 11:59, CHIGOT, CLEMENT via Gcc wrote:
> >
> > Hi everyone,
> >
> > I'm wondering if someone knows which tar version / configuration was being
> > used when creating gcc-10.2.0 tarballs ?
>
> GNU tar 1.30, I think.
I
On Tue, 28 Jul 2020 at 18:58, Josh Marshall via Gcc wrote:
>
> Hello,
>
> What are the forms and related legal stuff I need to fill out for
> contributions?
I'll send you these off-list.
On Sun, 2 Aug 2020 at 15:49, Philip R Brenan via Gcc wrote:
>
> Hi *GCC*:
>
> On page:
>
> https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html#Variadic-Macros
>
> you say:
>
> #define eprintf(args…) fprintf (stderr, args)
>
> but do you in fact mean:
>
> #define eprintf(args...) fprintf (stder
CC The gfortran list.
On Sat, 1 Aug 2020 at 23:38, Nino Pereira via Gcc wrote:
>
> https://gcc.gnu.org/onlinedocs/gfortran/INT.html#INT
>
> has two occurrences of 'or' next to each other.
>
> Arguments:
> A Shall be of type INTEGER, REAL, or COMPLEX or or a
> boz-literal-constant.
>
> HTH,
On Mon, 3 Aug 2020 at 11:28, Florian Weimer wrote:
>
> * Jonathan Wakely via Gcc:
>
> > On Sun, 2 Aug 2020 at 15:49, Philip R Brenan via Gcc
> > wrote:
> >>
> >> Hi *GCC*:
> >>
> >> On page:
> >>
> >> https://gcc.gn
On Mon, 3 Aug 2020 at 14:53, Richard Sandiford
wrote:
>
> Jonathan Wakely via Gcc writes:
> > On Mon, 3 Aug 2020 at 11:28, Florian Weimer wrote:
> >>
> >> * Jonathan Wakely via Gcc:
> >>
> >> > On Sun, 2 Aug 2020 at 15:49, Philip R Bre
On Fri, 7 Aug 2020 at 15:08, Luis Machado via Gcc wrote:
>
> Hi,
>
> cc-ing the GCC mailing list, as we may want to use the same coding style
> for GDB and GCC.
>
> Yesterday I brought this topic up on IRC. I notice we started using more
> and more the "auto" keyword. In some cases, this is actual
Hi Matt,
The best thing to do here is file a bug report with the code to reproduce it:
https://gcc.gnu.org/bugzill
Thanks
On Sat, 8 Aug 2020 at 23:01, Soul Studios wrote:
>
> Hi all,
> recently have been working on a new version of the plf::colony container
> (plflib.org) and found GCC9 was giv
On Tue, 11 Aug 2020 at 14:56, Nathan Sidwell wrote:
>
> On 8/7/20 10:06 AM, Luis Machado via Gcc wrote:
> > Hi,
> >
> > cc-ing the GCC mailing list, as we may want to use the same coding style
> > for GDB and GCC.
> >
> > Yesterday I brought this topic up on IRC. I notice we started using more
> >
On Wed, 12 Aug 2020 at 01:02, Paul Smith wrote:
>
> This is a kind of esoteric problem, but all the more annoying for that.
>
> As usual I've built my own version of GCC, and then I check it into Git
> so that all builds can use this one canonical compiler regardless of
> operating system, etc.
>
On Wed, 12 Aug 2020 at 14:33, Paul Smith wrote:
>
> I'm not talking about PREFIX/lib, though.
>
> As can be seen from my question I'm talking about
> PREFIX///lib. This is where GCC keeps its own
> internal libraries,
Not by default, it isn't. I'm not sure what directory that is, but
none of my
On Wed, 12 Aug 2020 at 17:43, Paul Smith wrote:
> However, the lib directory is empty in my build. What lives in your
> version of lib?
All the runtime libs, but I think that's because mingw doesn't use the
lib/lib64 split.
$ ls -1 ~/gcc/mingw/x86_64-w64-mingw32/lib/
libatomic-1.dll
libatomic.a
On Thu, 13 Aug 2020 at 07:46, Liu Hao via Gcc wrote:
>
> 在 2020/8/13 上午2:40, David Blaikie 写道:
> >
> > Then use of `auto*` would make it easier for you to spot use of plain
> > pointers in your projects & scrutinize them further?
> >
>
> My point is that `auto*` conveys no more information than `a
On Thu, 13 Aug 2020 at 08:52, Metzger, Markus T
wrote:
>
> Hello,
>
> > It seems like common sense to me. "Almost always use auto" is a silly
> > guideline. I can't stand seeing nonsense like:
> >
> > auto main() -> int
> > { ... }
>
> I personally do not like auto for reasons like the above or
>
This is the wrong mailing list for your question, please read
https://gcc.gnu.org/lists.html (and don't put your entire email in the
Subject: line please).
The MinGW compiler can be used to create console applications or GUI
applications. The default is -mconsole, which means the linker looks
for
On Thu, 13 Aug 2020 at 14:57, Dnyaneshwar Gomsale via Gcc
wrote:
>
> I am Dnyaneshwar Gomsale. I want to be the part of the your development
> team.
Great! We have a wiki page describing how to get started;
https://gcc.gnu.org/wiki/GettingStarted
On Wed, 19 Aug 2020 at 15:24, Bernd Eggen via Gcc wrote:
>
> Hello,
>
> I've come across an internal compiler error (in GFortran), concerning the
> function NINT(),
Then you should be reporting it to Bugzilla, not to this mailing list.
> Please submit a full bug report,
> with preprocessed sour
1 - 100 of 778 matches
Mail list logo
