Re: PR numbers from Changelogs do not arrive in bugzilla
* 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 up. Do the scripts recognize “PR fortran/67539” or just “PR 67539”? Thanks, Florian -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
Re: PR numbers from Changelogs do not arrive in bugzilla
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 commit body, not the commit subject are picked up. Yes, I have the same feeling.. Do the scripts recognize “PR fortran/67539” or just “PR 67539”? As I proved it was sent fine to gcc-reposurgeon-8 repo when I "repeated" the git commit. Martin Thanks, Florian
Re: -fstack-usage and -flto the stack usage report is generated
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 .su, are removed unless –save-temps is indicated. Although not obvious/not documented, but I am assuming this is working as designed. Developers should include –save-temps along with -fstack-suage and -flto. Thank you for the report. It seems it's a bug, please report it to bugzilla. Martin Or is this a bug? That is exception should be made for the ltrans.su files and they should be kept around regardless. Thanks, Visda
Re: -fstack-usage and -flto the stack usage report is generated
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 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 .su, are removed unless –save-temps is indicated. > > Although not obvious/not documented, but I am assuming this is working as designed. Developers should include –save-temps along with -fstack-suage and -flto. >>Thank you for the report. It seems it's a bug, please report it to bugzilla. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98922 >>Martin > > Or is this a bug? That is exception should be made for the ltrans.su files and they should be kept around regardless. > > Thanks, > Visda > Thanks, Visda
libstdc++-v3/doc/xml/manual/backwards_compatibility.xml
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 developers) or should this be trimmed quite a bit? Gerald
