-
Notifications
You must be signed in to change notification settings - Fork 559
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When running Configure, clang and clang++ produce different results #17133
Comments
From @jkeenan[The following is probably relevant to When I select '-Dcc=clang++', as distinct from '-Dcc=clang', ./Configure Suppose first that I configure blead ##### ... and then record the output of ./Configure in a file. Next, suppose I clean the checkout then reconfigure and re-record the ##### Here are the compiler versions: ##### clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final) If I diff the two output files, I get several differences, but the #####
./Configure composes and runs a number of C programs on the fly as ##### Line 10432 above is the source of the surprising output above that I got To answer one question in advance: There is no leading or trailing That implies that when running try.c, clang++ is calculating different To answer another question in advance: I don't get this difference when Is this a bug in clang++? Or is it a bug in ./Configure? Thank you very much. |
From @jkeenanSummary of my perl5 (revision 5 version 31 subversion 3) configuration: Characteristics of this binary (from libperl): |
From @doughera88On Sun, Aug 18, 2019 at 08:04:43AM -0700, James E Keenan (via RT) wrote:
It is a bug in Configure. The 'checkit()' program is declared to return There are probably other such C vs. C++ bugs in Configure, including d_futimes I will leave this bug open as I work on those. Thank you for noticing -- |
The RT System itself - Status changed from 'new' to 'open' |
On Dec 13 2019, Andy D. submitted 5 patches to
I then configured in the branch -- i.e., after applying the 5 patches -- with clang and then clang++ and compared those outputs.
Thank you very much. |
[snip]
Andy (@doughera88), are these differences between the results of configuration with clang and clang++, respectively, those that you would expect to remain after applying your five patches (as, e.g., in the If so, then I think we should apply those to blead and then (@Tux) apply them to metaconfig. Smoke-test results are satisfactory (i.e., no new failures caused by these patches). Another way of asking the same question: Can you list those problematic configuration differences that these patches resolve and those that you are still working on? Thank you very much. |
On Mon, Dec 16, 2019 at 07:11:25AM -0800, James E Keenan wrote:
> > \### From ***@***.***
> > On Sun, Aug 18, 2019 at 08:04:43AM -0700, James E Keenan (via RT) wrote:
> > > \# New Ticket Created by James E Keenan
> > > \# Please include the string: [perl #134375]
> > > \# in the subject line of all future correspondence about this issue.
> > > \# <URL: https://rt-archive.perl.org/perl5/Ticket/Display.html?id=134375 >
> > > [The following is probably relevant to
> > > https://rt-archive.perl.org/perl5/Ticket/Display.html?id=134371, but I'm filing it
> > > separately as it may be a more general problem.]
> > > When I select '-Dcc=clang++', as distinct from '-Dcc=clang', ./Configure
> > > produces different results. This difference appears to be independent
> > > of both operating system and other configuration options.
> >
> >
> > > Is this a bug in clang++? Or is it a bug in ./Configure?
> >
> >
> > It is a bug in Configure. The 'checkit()' program is declared to return
> > an integer, but actually returns nothing. (The return value is never used.)
> > This is undefined behavior in C++, but apparently not in C. See
> > https://bugs.llvm.org/show_bug.cgi?id=43075
> > for a simple test case and explanation.
> > There are probably other such C vs. C++ bugs in Configure, including
> > possibly the detection of
> > d_futimes
> > d_lchown
> > d_strtoll
> > d_strtoul
> > d_strtoull
> > d_strtouq
> > I will leave this bug open as I work on those. Thank you for noticing
> > this issue in the first place!
> > --
> > Andy Dougherty doughera@lafayette.edu
>
Andy ***@***.***), are these differences between the results of configuration with clang and clang++, respectively, those that you would expect to remain after applying your five patches (as, e.g., in the `smoke-me/jkeenan/andyd/configure-20191214` branch)?
If so, then I think we should apply those to blead and then ***@***.***) apply them to metaconfig. Smoke-test results are satisfactory (i.e., no new failures caused by these patches).
Another way of asking the same question: Can you list those problematic configuration differences that these patches resolve and those that you are still working on?
Thank you very much.
Jim Keenan
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#17133 (comment)
I've applied the patches to blead. I am not currently working on any other
related issues, so this ticket can be closed.
Thank you for following up on this,
…--
Andy Dougherty [email protected]
|
Thanks. I've taken the ticket for purpose of closing it after watching smoke test results. @Tux , @arc, @khwilliamson Can you apply these to metaconfig? Thank you very much. |
On Sun, Dec 29, 2019 at 04:10:08PM -0800, James E Keenan wrote:
> [snip]
> I've applied the patches to blead. I am not currently working on any other related issues, so this ticket can be closed. Thank you for following up on this,
> […](#)
> -- Andy Dougherty ***@***.***
Thanks. I've taken the ticket for purpose of closing it after watching smoke test results.
@Tux , @arc, @khwilliamson Can you apply these to metaconfig?
I'll look after the metaconfig patches next. They change some dependencies and
ordering, so there are a bit involved.
…--
Andy Dougherty [email protected]
|
On Sun, Dec 29, 2019 at 08:53:05PM -0500, Andy Dougherty wrote:
On Sun, Dec 29, 2019 at 04:10:08PM -0800, James E Keenan wrote:
> > [snip]
> > I've applied the patches to blead. I am not currently working on any other related issues, so this ticket can be closed. Thank you for following up on this,
> > […](#)
> > -- Andy Dougherty ***@***.***
>
> Thanks. I've taken the ticket for purpose of closing it after watching smoke test results.
>
> @Tux , @arc, @khwilliamson Can you apply these to metaconfig?
>
I'll look after the metaconfig patches next. They change some dependencies and
ordering, so there are a bit involved.
I think I've got it all pushed now. My dist installation apparently is
a bit out of sync so I can't test everything fully, but that's a task
for another day.
…--
Andy Dougherty [email protected]
|
Changes needed in blead were pushed by @doughera88 on Dec 29 2019. Closing ticket. Thank you very much. |
Migrated from rt.perl.org#134375 (status was 'open')
Searchable as RT134375$
The text was updated successfully, but these errors were encountered: