libstdc++-v3/doc/xml/manual/backwards_compatibility.xml

2021-02-01 Thread Gerald Pfeifer
I noticed this section on "Backwards Compatibility" in the libstdc++ docs that talks about - glibc 2.0.x - GCC 3.2 (August 2002) - GCC 4.1 (February 2006) and links to "Migrating to GCC 4.1" and "Migration guide for GCC-3.2" documents. Does this still make sense (and serve real users or deve

Re: -fstack-usage and -flto the stack usage report is generated

2021-02-01 Thread Visda.Vokhshoori--- via Gcc
On 2021-02-01, 3:19 AM, "Martin Liška" wrote: EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe On 1/29/21 3:57 PM, Visda.Vokhshoori--- via Gcc wrote: > > Hello, Hi. > > With link time optimization the stack usage informatio

Re: -fstack-usage and -flto the stack usage report is generated

2021-02-01 Thread Martin Liška
On 1/29/21 3:57 PM, Visda.Vokhshoori--- via Gcc wrote: Hello, Hi. With link time optimization the stack usage information is determined during local transformation and written to program.ltrans0.ltrans.su. There will be one .su file for each partition. All ltrans files, including the .s

Re: PR numbers from Changelogs do not arrive in bugzilla

2021-02-01 Thread Martin Liška
On 2/1/21 9:00 AM, Florian Weimer via Gcc wrote: * Thomas Koenig via Gcc: I had this problem previously, then it was thought that the messed-up spellling of my name caused this. That has been fixed by now. Any ideas what could be going wrong? On the glibc side, only bug references in the co

Re: PR numbers from Changelogs do not arrive in bugzilla

2021-02-01 Thread Florian Weimer via Gcc
* Thomas Koenig via Gcc: > I had this problem previously, then it was thought that the > messed-up spellling of my name caused this. That has been > fixed by now. > > Any ideas what could be going wrong? On the glibc side, only bug references in the commit body, not the commit subject are picked