Skip to content
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.

Sign up for GitHub

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

Jump to bottom

llvmc requires case-sensitive file system #1183

Closed
lattner opened this issue Jun 21, 2006 · 4 comments
Closed

llvmc requires case-sensitive file system #1183

lattner opened this issue Jun 21, 2006 · 4 comments
Labels
bugzilla Issues migrated from bugzilla build-problem llvm-tools All llvm tools that do not have corresponding tag portability

Comments

@lattner
Copy link
Collaborator

lattner commented Jun 21, 2006

Bugzilla Link 811
Resolution FIXED
Resolved on Feb 22, 2010 12:51
Version 1.5
OS MacOS X

Extended Description

This isn't a high priority or anything, but since it was reported to me, I might as well pass it on.

llvmc installs two files: "prefix/etc/llvm/c" and "prefix/etc/llvm/C" on the default MacOS X file system and
on windows, these two files will clobber each other because their file systems are case insensitive.

-Chris
@llvmbot
Copy link
Collaborator

llvmbot commented Jun 21, 2006

Okay, I'm going to drop the "C" and "cc" extensions as they aren't that common
for C++ code. This really needs to get clenaed up by not having these config
files at all (already filed in another bug).

@lattner
Copy link
Collaborator Author

lattner commented Jun 21, 2006

ah ok, that's the easy way to do it, thanks!

-Chris

@llvmbot
Copy link
Collaborator

llvmbot commented Jun 21, 2006

Fixed with this patch:
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20060619/035704.html

@lattner
Copy link
Collaborator Author

lattner commented Jun 21, 2006

nice! Thanks reid!

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 change SwplTargetMachine to AArch64SwplTargetMachine
0dc0b3b
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 add StmRegInfo
b4dc828
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 SwplScrのaarch64識別子対応
f381800
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 StmRegKindの固有処理を分離
3a829fd
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 canPipelineLoopをAArch64SwplTargetMachineへ移動
e3975bf
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 calcEachRegIncrementをAArch64SwplTargetMachineへ移動
c00ea71
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 未使用メソッドの削除
90579b0
kitano-metro pushed a commit to RIKEN-RCCS/llvm-project that referenced this issue Feb 14, 2023
@hakama2
refs llvm#1183 SeplRegからTIIに移動したcalcEachRegIncrementの修正
400458a
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla build-problem llvm-tools All llvm tools that do not have corresponding tag portability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lattner @llvmbot