Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] [RFC] Removal of 'deplibs'?"
2012 Nov 27
0
[LLVMdev] [cfe-dev] [RFC] Removal of 'deplibs'?
Please nuke it. It is really old and was never used. If it comes back it should be done with module metadata.
-Chris
On Nov 26, 2012, at 4:35 PM, Bill Wendling <wendling at apple.com> wrote:
> Hi all,
>
> Did you know that there is a 'deplibs' keyword? Neither did I. It looks like it's not really used for much. We don't document it in the Language Reference.
2012 Nov 28
2
[LLVMdev] [cfe-dev] [RFC] Removal of 'deplibs'?
Dears,
If you remove this keyword, will you keep the backward compatibility in
LLVM 3.x?
We use this keyword in our project for checking dependent libraries, and we
rely on the promise that bitcode format will keep compatible in LLVM
3.x. In our project, we compile and save bitcodes for later use, but we
always try to keep our runtime upstream. Hence, we need
readers recognize previous version
2013 Nov 25
2
[LLVMdev] Language Reference bug?
Hi,
The language reference uses "::" many places where it seems it should be
using ".. code-block:: llvm". The result is that Sphinx does not colorize
these samples.
Should I fix this? Or is it purposeful?
Also, anybody but me that has noticed that Sphinx does not always colorize
things even if you put the proper ".. code-block:: llvm" in front? If it
is a known
2012 Nov 28
0
[LLVMdev] [cfe-dev] [RFC] Removal of 'deplibs'?
On Nov 27, 2012, at 6:23 PM, Jason SH Lin <jasonlin.mtk at gmail.com> wrote:
> Dears,
>
> If you remove this keyword, will you keep the backward compatibility in LLVM 3.x?
>
> We use this keyword in our project for checking dependent libraries, and we rely on the promise that bitcode format will keep compatible in LLVM 3.x. In our project, we compile and save bitcodes for
2013 Nov 25
0
[LLVMdev] Language Reference bug?
On Sun, Nov 24, 2013 at 10:19 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote:
> Hi,
>
> The language reference uses "::" many places where it seems it should be
> using ".. code-block:: llvm". The result is that Sphinx does not colorize
> these samples.
>
> Should I fix this? Or is it purposeful?
>
Could you give an example of what you are
2012 Sep 19
8
[LLVMdev] [RFC] Overhauling Attributes
Overhauling Attributes
Problem
=======
LTO needs a way to pass options through to different parts of the compiler. In
particular, we need to pass code generation options to the back-end. The way we
want to do this is via the LLVM Attributes class. In order to do that, we need
to overhaul the Attributes class.
The Attributes class right now isn't very extensible. After considering several
2006 Mar 05
1
[LLVMdev] Keyword documenation for target, deplibs ...
Hello,
My goal is to create a language which can compile itself, therefore I
feel I need to understand the Assembler/Byte code format.
Starting with a C hello world program there are statements at the
beginning of the disassembled bc file that I couldn't find any
documentation:
target endian = little
target pointersize = 32
target triple = "i686-pc-linux-gnu"
2020 Jan 23
2
[cfe-dev] Phabricator -> GitHub PRs?
> On Jan 23, 2020, at 08:37, David Greene via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
> Hubert Tong <hubert.reinterpretcast at gmail.com> writes:
>
>>> I read this as the refresh being an entirely new GitHub PR. Is that
>>> right? Normally I would expect the same PR to be used but the rebase
>>> would cause a force-push of the branch
2020 Jan 22
3
[cfe-dev] Phabricator -> GitHub PRs?
On Wed, Jan 22, 2020 at 4:40 PM David Greene <greened at obbligato.org> wrote:
> Hubert Tong <hubert.reinterpretcast at gmail.com> writes:
>
> > The update process in Phab in rather manual and it does lead to more
> noise.
> > The GitHub force push risks loss of context for earlier comments (not
> just
> > in terms of display, like viewing older comments
2011 Feb 07
8
Pygments
The Pygments highlighter supports many more languages than CodeRay.
Pygments is written in Python, but I''ve seen non-Python projects use it
(Jekyll, Pygments).
There''s also this: https://github.com/nex3/rb-pygments
Any idea how much work it would be to add Pygments support to Webgen?
2008 Mar 27
1
R Code and the Pygments Python SyntaxHighlighter
Dear R Help,
is someone going to write a R/S language lexer for the Pygments Python syntax
highlighter <http://pygments.org/>? As it is used now by Trac, Django, or the
Python documentation tool Sphinx, the R community can apply it in Python-based
Wikis like Moinmoin and others.
Hans Werner
2019 May 09
3
failed to build llvm since 25de7691a0e27c29c8d783a22373cc265571f5e9 on AMD platform
LKP framework can guarantee that all the software environment are same on AMD and INTEL platform.
INTEL platform always work well, after revert this patch, AMD works well.
we tried below commit on AMD.
1) 25de7691a0e27c29c8d783a22373cc265571f5e9: bad
2) a82235843b102202766115e10003c9465a8b83ae: good
the error logs(build/CMakeFiles/CMakeError.log) has no difference b/w 1) and 2) on AMD platform
2009 Aug 19
2
[LLVMdev] Build issues on Solaris
Duncan Sands wrote:
> Hi Nathan,
>
>
>> The latter being what GenLibDeps.pl expects to see. All else being
>> equal though, it might be better to change GenLibDeps.pl to recognize
>> the first version:
>> --- GenLibDeps.pl (revision 78653)
>> +++ GenLibDeps.pl (working copy)
>> @@ -100,7 +100,7 @@
>> print "
2019 May 08
2
failed to build llvm since 25de7691a0e27c29c8d783a22373cc265571f5e9 on AMD platform
Hi
we observed that below errors occur on AMD platform since 25de7691a0e27c29c8d783a22373cc265571f5e9
root at lkp-opteron1 /opt/rootfs/llvm_project/src/build# cmake -DCMAKE_BUILD_TYPE=release -DLLVM_ENABLE_PROJECTS=clang -G "Unix Makefiles" ../llvm -DCMAKE_INSTALL_PREFIX=/opt/cross/
-- clang project is enabled
-- clang-tools-extra project is disabled
-- compiler-rt project is disabled
2012 Feb 11
2
[LLVMdev] shared bitcode modules / dynamic linking.
Hi,
afaics in manuals the llvm-{link,ld} tools only can merge bitcode files
into one bigger piece which looks like a static-linking from the c/c++ world.
i'm wondering is it any possibility to link bitcode elements dynamically
in the same way as e.g. c#/msil assemblies? static linking into one executable
looks horrible - any change in library used in project forces relinking of everything.
2012 Feb 26
0
[LLVMdev] shared bitcode modules / dynamic linking.
On Saturday 11 of February 2012 14:29:10 Paweł Sikora wrote:
> Hi,
>
> afaics in manuals the llvm-{link,ld} tools only can merge bitcode files
> into one bigger piece which looks like a static-linking from the c/c++ world.
> i'm wondering is it any possibility to link bitcode elements dynamically
> in the same way as e.g. c#/msil assemblies? static linking into one
2007 Sep 10
1
[LLVMdev] Weird Exception Handling Compilation Bug
On 9/10/07, Chris Lattner <sabre at nondot.org> wrote:
> On Mon, 10 Sep 2007, Bill Wendling wrote:
> > When I compile the following program with llvm-gcc on Mac x86, it segfaults:
> > However, if I compile it to a .s file and then compile it with gcc, it
> > works fine:
> > This is weird. Anyone have an idea of what's going on?
>
> They are probably
2011 Sep 22
2
[LLVMdev] question on difference of bitcode between C and C++
Could anybody provide me some links or pages or infos of the difference of
bitcodes of C and C++? We have implemented an optimization pass on bitcode
generated from C, and we are trying to find out whether it will work on
bitcode from C++. Thanks!
--
Best Regards,
Fei Jia
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Feb 25
5
[Cucumber] pretty html output?
Cucumberists (and RSpec Classic users ;):
How can we convert a Cucumber feature file into HTML with syntax highlighting?
Not the test-runner output; that''s preprocessed so it does not match the input
file...
Tx!
--
Phlip
2019 Dec 20
4
Upgrading from Debian Stretch to Buster, Van Belle package
Ah, ok,
apt-get remove libldb1 ldb-tools
Then try again : apt install samba winbind acl
The replacement of libldb1 to libldb2 is missing something.
I'll have a look at that.
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: Lmloge [mailto:lmloge at orange.fr]
> Verzonden: vrijdag 20 december 2019 13:15
> Aan: L.P.H. van Belle
> CC: samba at lists.samba.org