Re: Please support Coroutines TS in C++

2017-10-16 Thread Nathan Sidwell
On 10/16/2017 07:06 AM, Jonathan Wakely wrote: On 16 October 2017 at 08:25, Ramón García wrote: ping As previously stated, nobody is working on it. Not because nobody cares, but because of lack of time against higher priority things. nathan -- Nathan Sidwell

Re: -ffunction-sections and -fdata-sections documentation

2017-10-16 Thread Sebastian Huber
On 16/10/17 12:31, David Brown wrote: On 13/10/17 09:06, Sebastian Huber wrote: Hello, I would like to update the documentation of these compiler flags and have some questions. The -ffunction-sections and -fdata-sections documentation is currently: Do these options affect the code generati

Re: Please support Coroutines TS in C++

2017-10-16 Thread Jonathan Wakely
On 16 October 2017 at 08:25, Ramón García wrote: > ping As previously stated, nobody is working on it. GCC is Free Software, so if you really need ths feature you are free to add it yourself. > > On Thu, Aug 31, 2017 at 11:22 AM, Ramón García > wrote: >> (repeated, forgot to reply to mailing

Re: Questions about a patch fixing bug #61414

2017-10-16 Thread Sam van Kampen via gcc
On Mon, Oct 16, 2017 at 01:06:04AM +0100, Jonathan Wakely wrote: > On 14 October 2017 at 17:19, Sam van Kampen via gcc wrote: > > On Sat, Oct 14, 2017 at 04:43:33PM +0100, Jonathan Wakely wrote: > >> On 14 October 2017 at 15:50, Sam van Kampen wrote: > >> > Dear maintainers, > >> > > >> > Having c

Re: -ffunction-sections and -fdata-sections documentation

2017-10-16 Thread David Brown
On 13/10/17 09:06, Sebastian Huber wrote: > Hello, > > I would like to update the documentation of these compiler flags and > have some questions. The -ffunction-sections and -fdata-sections > documentation is currently: > > Do these options affect the code generation? > -fdata-sections certa

Re: Please support Coroutines TS in C++

2017-10-16 Thread Ramón García
ping On Thu, Aug 31, 2017 at 11:22 AM, Ramón García wrote: > (repeated, forgot to reply to mailing list) > > Xi Ruoyao misses completely the point! > > The amount of error prone boilerplate code, that the programmer would > have to write, is huge. See examples in the excellent presentation > "C++