LOGIN   :::   RECOVER PASS   :::   GET ACCOUNT    
Browse
  • Projects
  • Code (CVS)
  • Forums
  • News
  • Articles
  • Polls
  •  
    OpenCores
  • FAQ
  • CVS HowTo
  • Mission
  • Media
  • Tools
  • Advertise
  • Mirrors
  • Logos
  • Contact us
  • Find Resources
  • Job Opportunity
  •  
    Tools
  • Search
      
  • Download Cores (CVSGet)
  •  
    More
  • Wishbone
  • Perlilog
  • EDA tools
  • OpenTech CD
  •  
    Navigation: All forums > Openrisc > Message List > Message Post

    Message

    Reply | Reply all
    Date Prev | Date Next | Thread Prev | Thread Next Date Index | Thread Index

    From: Balint Cristian<rezso@r...>
    Date: Sat Feb 19 19:50:34 CET 2005
    Subject: [openrisc] x86_64 linux [more]
    Top
    On Saturday 19 February 2005 02:46, Matjaz Breskvar wrote:
    > Hi,
    >
    > i currently don't have access to x86_64 machine, so can you provide some
    > more information please.
    >
    > the complete genereted *.s file would be nice... what i'm looking for is
    > a pattern where the problem happens....


    Ok i found where that is emmited:

    or32.c --> line 469,

    else if (GET_CODE (operands[1]) == CONST_INT)
    {
    if (INTVAL (operands[1]) < 0)
    output_asm_insn ("\tl.addi \t%0, r0, -1", operands);
    else
    output_asm_insn ("\tl.or \t%0, r0, r0", operands);
    output_asm_insn ("\tl.movhi \t%H0, hi(%1)", operands);
    output_asm_insn ("\tl.ori \t%H0, %H0, lo(%1)", operands);
    printf ("\nOperands: %d \n", operands);

    return "";
    }

    That still doesnt help me, i dont know these code lines what do exactly.

    Hmm please also take a look to the emmited asm code, there are lots of values
    with "-" minus, and looks very strange.

    Any help would be great.
    ~cristian

    ReferenceAuthor
    [openrisc] gcc-3.4.2 uncompileable on x86_64 linuxMatjaz Breskvar

    Follow upAuthor
    [openrisc] x86_64 linux [more&more]Balint Cristian

     
    Copyright (c) 1999 OPENCORES.ORG. All rights reserved.