This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Indexes: [Date Index] [Subject Index] [Author Index] [Thread Index] Site Nav: [Browse other archives for this mailing list]
[Browse other mailing lists at this site]
March 31, 2019
22:42 | gcc-9-20190331 is now available | gccadmin |
18:08 | Re: Status of all 3 aktiv bracnhes on x86_64-w64-mingw32. | Óscar Fuentes |
17:41 | Re: syncing the GCC vax port | coypu |
17:26 | Re: syncing the GCC vax port | Paul Koning |
15:39 | [GSoC 2019] Proposal: Parallelize GCC With Threads | Giuliano Belinassi |
March 30, 2019
11:24 | Re: About GSOC. | Tejas Joshi |
10:42 | Re: programming language that does not inhibit further optimization by gcc | David Brown |
09:03 | syncing the GCC vax port | coypu |
08:54 | Status of all 3 aktiv bracnhes on x86_64-w64-mingw32. | Rainer Emrich |
07:14 | Re: programming language that does not inhibit further optimization by gcc | Albert Abramson |
March 29, 2019
22:41 | gcc-8-20190329 is now available | gccadmin |
22:29 | FIXME in gcc/gimplify.c | nick |
17:00 | Re: GSOC Proposal | nick |
14:28 | Re: GSOC Proposal | nick |
12:26 | GCC 9 Status Report (2019-03-29) | Richard Biener |
09:08 | Re: GSOC Proposal | Richard Biener |
08:48 | Re: GSOC | Richard Biener |
04:01 | Re: GCC GSOC 2019 | Shubham Narlawar |
March 28, 2019
22:40 | gcc-7-20190328 is now available | gccadmin |
20:20 | Re: GSOC | Giuliano Belinassi |
13:38 | Re: GSOC Proposal | nick |
10:09 | [GSoC] | Avinash Tiwary |
08:59 | Re: GSOC Proposal | Richard Biener |
08:44 | Re: GSOC | Richard Biener |
08:42 | Re: GSOC | Richard Biener |
08:27 | Re: GCC-Reordering-Optimization-Options in Os and O2 when using __builtin_expect() and documentation | Richard Biener |
06:07 | Re: Warning for C Parameter Name Mismatch | Eric Gallager |
March 27, 2019
March 26, 2019
March 25, 2019
23:51 | GSOC | nick |
23:32 | Re: [GSoC 2019] No application template? | Martin Jambor |
21:39 | Re: Warning in gcc/libiberty/dyn-string.c during build | nick |
19:45 | Re: Warning in gcc/libiberty/dyn-string.c during build | Jeff Law |
19:22 | Gsoc | FuN traveller |
16:39 | Re: Warning in gcc/libiberty/dyn-string.c during build | Martin Sebor |
14:16 | Re: Gcov Internals | Nathan Sidwell |
14:14 | Regarding GSOC | Aniket Agarwalla |
13:36 | Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla | nick |
13:30 | Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla | Jonathan Wakely |
13:26 | Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla | nick |
13:25 | Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla | Jonathan Wakely |
12:39 | [PATCH] Proposed patch to fix bug id, 89796 on bugzilla | Nicholas Krause |
12:36 | GCC-Reordering-Optimization-Options in Os and O2 when using __builtin_expect() and documentation | Moritz Strübe |
05:05 | Link Building Service | Backlinks Service | Guest Post Service | | Marco |
March 24, 2019
22:42 | gcc-9-20190324 is now available | gccadmin |
19:33 | Re: [GSoC 2019] [extending Csmith for fuzzing OpenMp extensions] | sameeran joshi |
09:49 | Solicitud de Cotización | Patricia Ortega |
06:29 | [GSoC 2019] No application template? | 김규래 |
05:35 | Bugzilla ID 88395 | nick |
03:49 | Warning in gcc/libiberty/dyn-string.c during build | nick |
02:55 | Re: [GSoC 2019] [extending Csmith for fuzzing OpenMp extensions] | Andi Kleen |
00:50 | Re: GCC 4.8.1 unable to compile a .c File | Vinaya Dandur |
March 23, 2019
18:24 | Re: GCC 4.8.1 unable to compile a .c File | Paul Smith |
18:19 | Re: [GSoC 2019] [extending Csmith for fuzzing OpenMp extensions] | sameeran joshi |
17:25 | Re: GCC 4.8.1 unable to compile a .c File | Vinaya Dandur |
17:08 | Re: GCC 4.8.1 unable to compile a .c File | Jonathan Wakely |
16:46 | Re: GCC 4.8.1 unable to compile a .c File | Paul Smith |
16:26 | GSoC | youssef Elmasry |
16:25 | Re: GCC 4.8.1 unable to compile a .c File | Vinaya Dandur |
16:22 | Re: GCC 4.8.1 unable to compile a .c File | Jonathan Wakely |
15:14 | GCC 4.8.1 unable to compile a .c File | Vinaya Dandur |
March 22, 2019
March 21, 2019
22:40 | gcc-7-20190321 is now available | gccadmin |
22:31 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Jakub Jelinek |
22:20 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Allan Sandfeld Jensen |
09:52 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Andrew Haley |
09:34 | Re: Indicating function exit points in debug data | Justin Paston-Cooper |
09:11 | Re: Indicating function exit points in debug data | Justin Paston-Cooper |
08:54 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Moritz Strübe |
08:35 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Richard Biener |
08:25 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Alexander Monakov |
08:23 | Re: Indicating function exit points in debug data | Richard Biener |
08:17 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Richard Biener |
01:20 | Re: RISC-V sibcall optimization with save-restore | Jim Wilson |
March 20, 2019
19:05 | Re: Indicating function exit points in debug data | Tom Tromey |
17:36 | Re: Indicating function exit points in debug data | Segher Boessenkool |
17:36 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Andrew Haley |
15:49 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Jakub Jelinek |
15:39 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Moritz Strübe |
14:26 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Christophe Lyon |
14:18 | AUVSI XPONENTIAL 2019 - Attendees | Martha Daxer |
14:08 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Moritz Strübe |
12:25 | RISC-V sibcall optimization with save-restore | Paulo Matos |
10:13 | Re: Indicating function exit points in debug data | Justin Paston-Cooper |
09:43 | Re: ITHELPDESK | Kristina Naumovski |
08:31 | Re: Indicating function exit points in debug data | Richard Biener |
08:27 | Re: A bug in vrp_meet? | Richard Biener |
March 19, 2019
22:52 | Re: Indicating function exit points in debug data | Justin Paston-Cooper |
22:40 | Re: Indicating function exit points in debug data | Florian Weimer |
22:20 | Re: Indicating function exit points in debug data | Justin Paston-Cooper |
21:52 | Re: Indicating function exit points in debug data | Florian Weimer |
21:41 | Re: Indicating function exit points in debug data | Justin Paston-Cooper |
21:29 | Re: Indicating function exit points in debug data | Florian Weimer |
20:38 | Indicating function exit points in debug data | Justin Paston-Cooper |
19:53 | Re: A bug in vrp_meet? | Jeff Law |
March 18, 2019
14:19 | [WIP][RFC] split of i386.c | Martin Liška |
March 17, 2019
22:40 | gcc-9-20190317 is now available | gccadmin |
14:51 | Re: Bug gives no stack trace on segfault | nick |
10:50 | Re: Bug gives no stack trace on segfault | Jonathan Wakely |
00:21 | Bug gives no stack trace on segfault | nick |
March 15, 2019
22:40 | gcc-8-20190315 is now available | gccadmin |
17:12 | Fwd: | Bruce Adams |
04:20 | GSOC | nick |
March 14, 2019
22:39 | gcc-7-20190314 is now available | gccadmin |
21:28 | GNU Tools Cauldron 2019 | Simon Marchi |
20:01 | GSoC | Matias Barrientos |
11:56 | Re: Linking against libgcc.a on GNU/Linux | Florian Weimer |
09:51 | Re: Linking against libgcc.a on GNU/Linux | Florian Weimer |
March 13, 2019
22:53 | BmExl幵XOdI真jL票eVDX | 佃郁瘤 |
17:46 | Re: Linking against libgcc.a on GNU/Linux | Joseph Myers |
16:22 | Re: debugging libgo failures | Aldy Hernandez |
13:56 | Re: [RFC] split of i386.c | Uros Bizjak |
12:55 | Re: [RFC] split of i386.c | David Malcolm |
10:18 | Re: GCC turns &~ into | due to undefined bit-shift without warning | David Brown |
09:36 | Linking against libgcc.a on GNU/Linux | Florian Weimer |
06:47 | GSOC -willing to work on a project idea for GCC | Dinesh ch |
02:51 | GIMPLE type and Architecture | dalas |
02:25 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Vincent Lefevre |
March 12, 2019
20:57 | Re: GCC turns &~ into | due to undefined bit-shift without warning | David Brown |
20:54 | Re: [RFC] split of i386.c | Jeff Law |
20:54 | Re: How to add %' into gfc_fatal_error | Eric Gallager |
20:50 | Re: [RFC] split of i386.c | Eric Gallager |
19:28 | Re: debugging libgo failures | Ian Lance Taylor |
18:20 | debugging libgo failures | Aldy Hernandez |
15:40 | Re: GCC turns &~ into | due to undefined bit-shift without warning | Vincent Lefevre |
15:09 | Re: How to add %' into gfc_fatal_error | Martin Liška |
15:08 | [RFC] split of i386.c | Martin Liška |
14:17 | Re: How to add %' into gfc_fatal_error | Steve Kargl |
11:15 | Re: How to add %' into gfc_fatal_error | Martin Liška |
08:08 | Re:2018-12-26 | Sales29 at dake dot com |
07:04 | [GSoC 2019]: Interested in "Make C/C++ not automatically promote memory_order_consume to memory_order_acquire" | Akshatg |
March 11, 2019
March 10, 2019
22:40 | gcc-9-20190310 is now available | gccadmin |
18:54 | GSoC | Martin Emil |
12:05 | Re: Warning for C Parameter Name Mismatch | Basile Starynkevitch |
11:54 | Re: Warning for C Parameter Name Mismatch | David Brown |
06:11 | Re: Warning for C Parameter Name Mismatch | Basile Starynkevitch |
March 09, 2019
21:58 | 合C法R经f营W | ptzv |
17:51 | Re: Warning for C Parameter Name Mismatch | Joel Sherrill |
17:27 | Re: Warning for C Parameter Name Mismatch | Segher Boessenkool |
12:22 | Re: Warning for C Parameter Name Mismatch | David Brown |
08:30 | Re: Warning for C Parameter Name Mismatch | Jonathan Wakely |
02:23 | Re: Warning for C Parameter Name Mismatch | Eric Gallager |
March 08, 2019
23:36 | Re: Warning for C Parameter Name Mismatch | David Brown |
23:06 | Re: Warning for C Parameter Name Mismatch | Joseph Myers |
22:59 | Re: Ryzen PPA znver1 optimizations | Vanida Plamondon |
22:44 | Re: Ryzen PPA znver1 optimizations | Jonathan Wakely |
22:40 | gcc-8-20190308 is now available | gccadmin |
22:25 | Warning for C Parameter Name Mismatch | Joel Sherrill |
22:00 | Re: Ryzen PPA znver1 optimizations | Vanida Plamondon |
20:58 | Re: Ryzen PPA znver1 optimizations | Jonathan Wakely |
11:52 | GCC 9 Usability Improvements blog post | David Malcolm |
11:28 | Re: Ryzen PPA znver1 optimizations | Vanida Plamondon |
11:00 | Re: Ryzen PPA znver1 optimizations | Richard Biener |
10:35 | Re: GSoC Project Ideas | Richard Biener |
07:56 | Ryzen PPA znver1 optimizations | Vanida Plamondon |
March 07, 2019
23:53 | Re: Signed-unsigned comparison question | Zoltan Kocsi |
23:40 | Signed-unsigned comparison question | Zoltan Kocsi |
22:40 | gcc-7-20190307 is now available | gccadmin |
18:20 | Re: GSoC Project Ideas | Martin Sebor |
12:47 | Re: A bug in vrp_meet? | Richard Biener |
March 06, 2019
13:43 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | Alexander Potapenko via gcc |
13:11 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | David Brown |
10:06 | Re: A bug in vrp_meet? | Richard Biener |
03:43 | Thank you! | SaapVer |
01:51 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | Segher Boessenkool |
March 05, 2019
23:08 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | Mark Wielaard |
21:36 | Re: A bug in vrp_meet? | Jeff Law |
21:27 | Re: A bug in vrp_meet? | Jeff Law |
21:17 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | Martin Sebor |
21:17 | Re: A bug in vrp_meet? | Jeff Law |
20:37 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | David Brown |
18:37 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | Segher Boessenkool |
17:08 | Re: [RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically | Joseph Myers |
15:43 | Re: GSoC Project Ideas | Eric Gallager |
14:45 | Re: A bug in vrp_meet? | Richard Biener |
11:10 | Re: [RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically | JunMa |
10:44 | Re: A bug in vrp_meet? | Richard Biener |
09:55 | Re: [RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically | Richard Biener |
09:48 | Re: A bug in vrp_meet? | Richard Biener |
09:41 | [RFC] gcc lto&binutils: Load different gcc's bfd-plugin automatically | JunMa |
March 04, 2019
22:01 | Re: A bug in vrp_meet? | Qing Zhao |
20:46 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | David Brown |
16:09 | Re: A bug in vrp_meet? | Qing Zhao |
13:17 | Re: GSoC Project Ideas | Richard Biener |
12:23 | Re: GSoC Project Ideas | Jakub Jelinek |
12:13 | Re: GSoC Project Ideas | Richard Biener |
12:02 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | Richard Biener |
11:45 | Re: A bug in vrp_meet? | Richard Biener |
10:57 | Re: GSoC Project Ideas | P J P |
10:44 | Re: About BZ#87210 [RFE] To initialize automatic stack variables | P J P |
March 03, 2019
23:16 | Re: GSoC Project Ideas | Jeff Law |
23:06 | GSoC Project Ideas | Patrick Palka |
22:41 | gcc-9-20190303 is now available | gccadmin |
March 02, 2019
17:16 | Re: Implementing an algorithm in place of gomp 'auto' | 김규래 |
16:48 | Re: Implementing an algorithm in place of gomp 'auto' | Jakub Jelinek |
13:05 | Re: Implementing an algorithm in place of gomp 'auto' | 김규래 |
March 01, 2019
22:40 | gcc-8-20190301 is now available | gccadmin |
22:04 | Re: GSoC | Dmitry Mikushin |
21:02 | Re: A bug in vrp_meet? | Qing Zhao |
20:08 | GSoC | Ahmed Ashraf |
19:25 | Re: A bug in vrp_meet? | Richard Biener |
17:49 | Re: A bug in vrp_meet? | Qing Zhao |
17:46 | Re: Implementing an algorithm in place of gomp 'auto' | Jakub Jelinek |
17:40 | Re: Implementing an algorithm in place of gomp 'auto' | 김규래 |
17:32 | Re: Implementing an algorithm in place of gomp 'auto' | Jakub Jelinek |
14:40 | Implementing an algorithm in place of gomp 'auto' | 김규래 |
Indexes: [Date Index] [Subject Index] [Author Index] [Thread Index] Site Nav: [Browse other archives for this mailing list]
[Browse other mailing lists at this site]