en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#7068aa98 Strengthen -Wint-conversion to default to an errorClang has traditionally allowed C programs to implicitly convertintegers to pointers and pointers to integers, despite it not beingvalid to do so except under special circumstances (like converting theinteger 0, which is the null pointer constant, to a pointer). In C89,this would result in undefined behavior per 3.3.4, and in C99 this rulewas strengthened to be a constraint violation instead. Constraintviolations are most often handled as an error.This patch changes the warning to default to an error in all C modes(it is already an error in C++). This gives us better security postureby calling out potential programmer mistakes in code but still allowsusers who need this behavior to use -Wno-error=int-conversion to retainthe warning behavior, or -Wno-int-conversion to silence the diagnosticentirely.Differential Revision: https://reviews.llvm.org/D129881 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Fri, 22 Jul 2022 19:24:54 +0000 Aaron Ballman <aaron@aaronballman.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#532dc62b [OpaquePtrs][Clang] Add -no-opaque-pointers to tests (NFC)This adds -no-opaque-pointers to clang tests whose output willchange when opaque pointers are enabled by default. This isintended to be part of the migration approach described inhttps://discourse.llvm.org/t/enabling-opaque-pointers-by-default/61322/9.The patch has been produced by replacing %clang_cc1 with%clang_cc1 -no-opaque-pointers for tests that fail with opaquepointers enabled. Worth noting that this doesn't cover all tests,there's a remaining ~40 tests not using %clang_cc1 that will needa followup change.Differential Revision: https://reviews.llvm.org/D123115 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Thu, 07 Apr 2022 10:03:55 +0000 Nikita Popov <npopov@redhat.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#ed509fe2 Use functions with prototypes when appropriate; NFCA significant number of our tests in C accidentally use functionswithout prototypes. This patch converts the function signatures to havea prototype for the situations where the test is not specific to K&R Cdeclarations. e.g., void func();becomes void func(void);This is the tenth batch of tests being updated (there are asignificant number of other tests left to be updated). List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Tue, 15 Feb 2022 14:27:12 +0000 Aaron Ballman <aaron@aaronballman.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#aee49255 Recommit: Compress formatting of array type names (int [4] -> int[4])Based on post-commit review discussion on2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith.Other uses of forcing HasEmptyPlaceHolder to false seem OK to me -they're all around pointer/reference types where the pointer/referencetoken will appear at the rightmost side of the left side of the typename, so they make nested types (eg: the "int" in "int *") behave asthough there is a non-empty placeholder (because the "*" is essentiallythe placeholder as far as the "int" is concerned).This was originally committed in 277623f4d5a672d707390e2c3eaf30a9eb4b075cReverted in f9ad1d1c775a8e264bebc15d75e0c6e5c20eefc7 due to breakagesoutside of clang - lldb seems to have some strange/strong dependence on"char [N]" versus "char[N]" when printing strings (not due to that nameappearing in DWARF, but probably due to using clang to stringify typenames) that'll need to be addressed, plus a few other odds and ends inother subprojects (clang-tools-extra, compiler-rt, etc). List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Thu, 14 Oct 2021 21:52:47 +0000 David Blaikie <dblaikie@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#f9ad1d1c Revert "Compress formatting of array type names (int [4] -> int[4])"Looks like lldb has some issues with this - somehow it causes lldb totreat a "char[N]" type as an array of chars (prints them outindividually) but a "char [N]" is printed as a string. (even though theDWARF doesn't have this string in it - it's something to do with thestring lldb generates for itself using clang)This reverts commit 277623f4d5a672d707390e2c3eaf30a9eb4b075c. List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Thu, 14 Oct 2021 21:48:17 +0000 David Blaikie <dblaikie@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#277623f4 Compress formatting of array type names (int [4] -> int[4])Based on post-commit review discussion on2bd84938470bf2e337801faafb8a67710f46429d with Richard Smith.Other uses of forcing HasEmptyPlaceHolder to false seem OK to me -they're all around pointer/reference types where the pointer/referencetoken will appear at the rightmost side of the left side of the typename, so they make nested types (eg: the "int" in "int *") behave asthough there is a non-empty placeholder (because the "*" is essentiallythe placeholder as far as the "int" is concerned). List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Thu, 14 Oct 2021 21:07:51 +0000 David Blaikie <dblaikie@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#fd739804 [test] Add {{.*}} to make ELF tests immune to dso_local/dso_preemptable/(none) differencesFor a default visibility external linkage definition, dso_local is set for ELF-fno-pic/-fpie and COFF and Mach-O. Since default clang -cc1 for ELF is similarto -fpic ("PIC Level" is not set), this nuance causes unneeded binary format differences.To make emitted IR similar, ELF -cc1 -fpic will default to -fno-semantic-interposition,which sets dso_local for default visibility external linkage definitions.To make this flip smooth and enable future (dso_local as definition default),this patch replaces (function) `define ` with `define{{.*}} `,(variable/constant/alias) `= ` with `={{.*}} `, or inserts appropriate `{{.*}} `. List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Thu, 31 Dec 2020 08:27:11 +0000 Fangrui Song <i@maskray.me> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#9658d895 [Sema] Adds the pointer-to-int-cast diagnosticConverting a pointer to an integer whose result cannot represented in theinteger type is undefined behavior is C and prohibited in C++. C++ alreadyhas a diagnostic when casting. This adds a diagnostic for C.Since this diagnostic uses the range of the conversion it also modifiesint-to-pointer-cast diagnostic to use a range.Fixes PR8718: No warning on casting between pointer and non-pointer-sized intDifferential Revision: https://reviews.llvm.org/D72231 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Sun, 16 Feb 2020 14:01:25 +0000 Mark de Wever <koraq@xs4all.nl> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#dbc96b51 Revert "[CodeGenModule] Assume dso_local for -fpic -fno-semantic-interposition"This reverts commit 789a46f2d742e11edaade28cb59a0f4d2a1d770e.Accidentally committed. List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Mon, 03 Feb 2020 18:09:39 +0000 Fangrui Song <maskray@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#789a46f2 [CodeGenModule] Assume dso_local for -fpic -fno-semantic-interpositionSummary:Clang -fpic defaults to -fno-semantic-interposition (GCC -fpic defaultsto -fsemantic-interposition).Users need to specify -fsemantic-interposition to get semanticinterposition behavior.Semantic interposition is currently a best-effort feature. There maystill be some cases where it is not handled well.Reviewers: peter.smith, rnk, serge-sans-paille, sfertile, jfb, jdoerfertSubscribers: dschuff, jyknight, dylanmckay, nemanjai, jvesely, kbarton, fedor.sergeev, asb, rbar, johnrusso, simoncook, sabuasal, niosHD, jrtc27, zzheng, edward-jones, atanasyan, rogfer01, MartinMosbeck, brucehoult, the_o, arphaman, PkmX, jocewei, jsji, Jim, lenary, s.egerton, pzheng, sameer.abuasal, apazos, luismarques, cfe-commitsTags: #clangDifferential Revision: https://reviews.llvm.org/D73865 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Sun, 02 Feb 2020 20:23:47 +0000 Fangrui Song <maskray@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#9864269a Fix reliance on lax vector conversions in tests for x86 intrinsics.llvm-svn: 372062 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Tue, 17 Sep 2019 03:56:28 +0000 Richard Smith <richard-llvm@metafoo.co.uk> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#3f82f9e1 [CodeGen] Always use string computed in Sema for PredefinedExprWe can't use any other string, anyway, because its type wouldn'tmatch the type of the PredefinedExpr.With this change, we don't compute a "nice" name for the __func__ globalwhen it's used in the initializer for a constant. This doesn't seem likea great loss, and I'm not sure how to fix it without either storing moreinformation in the AST, or somehow threading through the informationfrom ExprConstant.cpp.This could break some situations involving BlockDecl; currently,CodeGenFunction::EmitPredefinedLValue has some logic to intentionallyemit a string different from what Sema computed. This code skips thatlogic... but that logic can't work correctly in general anyway. (Forexample, sizeof(__func__) returns the wrong result.) Hopefully thisdoesn't affect practical code.Fixes https://bugs.llvm.org/show_bug.cgi?id=40313 .Differential Revision: https://reviews.llvm.org/D56821llvm-svn: 351766 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Tue, 22 Jan 2019 00:11:17 +0000 Eli Friedman <efriedma@codeaurora.org> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#3f1d6de4 Revert r332847; it caused us to miscompile certain forms of reference initialization.llvm-svn: 332886 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Mon, 21 May 2018 20:36:58 +0000 Richard Smith <richard-llvm@metafoo.co.uk> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#9f806842 [CodeGen] Recognize more cases of zero initializationIf a variable has an initializer, codegen tries to build its value. Ifthe variable is large in size, building its value requires substantialresources. It causes strange behavior from user viewpoint: compilationof huge zero initialized arrays like: char data_1[2147483648u] = { 0 };consumes enormous amount of time and memory.With this change codegen tries to determine if variable initializer isequivalent to zero initializer. In this case variable value is notconstructed.This change fixes PR18978.Differential Revision: https://reviews.llvm.org/D46241llvm-svn: 332847 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Mon, 21 May 2018 16:09:54 +0000 Serge Pavlov <sepavloff@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#3370c20c [CodeGen] Use pointer-sized integers for ptrtoint sourcesGiven something like:void *v = (void *)100;We need to synthesize a ptrtoint operation from 100. During constantemission, we choose i64 as the type for our constant because itguaranteed not to drop any bits from our CharUnits representation of thevalue. However, this is suboptimal for 32-bit targets: LLVM passes likeGlobalOpt will get confused by these sorts of casts resulting inpessimization.Instead, make sure the ptrtoint operand has a pointer-sized integertype.llvm-svn: 273020 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Fri, 17 Jun 2016 17:47:24 +0000 David Majnemer <david.majnemer@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#bdf40a62 Test case updates for explicit type parameter to the gep operatorllvm-svn: 232187 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Fri, 13 Mar 2015 18:21:46 +0000 David Blaikie <dblaikie@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#8e133965 CodeGen: ConstStructBuilder must verify packed constraints after paddingThis reverts commit r220169 which reverted r220153. However, it alsocontains additional changes:- We may need to add padding *after* we've packed the struct. This occurs when the aligned next field offset is greater than the new field's offset. When this occurs, we make the struct packed. *However*, once packed the next field offset might be less than the new feild's offset. It is in this case that we might further pad the struct.- We would pad structs which were perfectly sized! This behavior is immensely old. This behavior came from blindly subtracting NextFieldOffsetInChars from RecordSize. This doesn't take into account the fact that the struct might have a greater overall alignment than the last field.llvm-svn: 220175 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Sun, 19 Oct 2014 23:40:06 +0000 David Majnemer <david.majnemer@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#bf972bb2 Revert r220153: "CodeGen: ConstStructBuilder must verify packed constraints after padding"This commit caused two tests in LNT to regress. I'm able to reproduce onany platform and will send reproduction steps to the original commitlog. This should restore the LNT bots that have been failing.llvm-svn: 220169 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Sun, 19 Oct 2014 19:41:46 +0000 Chandler Carruth <chandlerc@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#afefe97e CodeGen: ConstStructBuilder must verify packed constraints after paddingBefore, ConstStructBuilder::AppendBytes would check packed constraintsprior to padding being added before the field's offset. However, addingthis padding might force our struct to be packed. Because we wouldn'tcheck *after* adding padding, ConstStructBuilder would be in aninconsistent state leading to a crash.This fixes PR21300.llvm-svn: 220153 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Sun, 19 Oct 2014 00:03:10 +0000 David Majnemer <david.majnemer@gmail.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/clang/test/CodeGen/const-init.c#87627034 Add missing expected-warning.llvm-svn: 185644 List of files: /llvm-project-15.0.7/clang/test/CodeGen/const-init.c Thu, 04 Jul 2013 15:04:25 +0000 Rafael Espindola <rafael.espindola@gmail.com>